<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><div><br></div><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><br><div style="font-family: arial,helvetica,sans-serif; font-size: 13px;">----- Forwarded Message ----<br>From: Bruce M Simpson <bms@incunabulum.net><br>To: Nguyen Van Nam <van_nam_78@yahoo.com><br>Cc: XORP DEVELOPERS <xorp-hackers@icir.org><br>Sent: Monday, August 4, 2008 12:05:45 AM<br>Subject: Re: [Xorp-hackers] Conflict between processes, how to avoid?<br><br>
Nguyen Van Nam wrote:<br>> Hi all,<br>> Thank you so much for your answers.<br>> In fact, i have implemented a XRL client interface to notify LSDB change.<br>> But I have encountered an error when I called another Xrl request to <br>> set interface cost, because this one cause the LSDB to be changed<br>> immediately so at the same time there are 2 processes running. In your <br>> experiences , how to avoid this?<br><br>XRLs can only be processed one at a time by any XORP process, as they <br>are all single threaded.<br><br>How exactly is the race condition manifesting in your program, and how <br>is this a problem? It would be helpful for others if you point out <br>exactly which error(s) you're seeing.<br><br>It is not going to be possible to avoid having the Lsa database change <br>from underneath the xorp_ospf process, obviously because setting the <br>interface cost changes the cost of Lsas (and their corresponding routing
<br>table entries) which transit that interface.<br><br>thanks<br>BMS<br></div></div></div><br>
</body></html>