You can do all that just by not setting Handler::NONEXCLUSIVE. If your timing constraints are so tight that you can't allow for the possibility that your Click thread will be blocked by your user thread (which would happen with a spinlock, too), then I guess you need to make a little lock-free work queue in your element. Have your handler add the description of what to do to the work queue, and have your task pull the description off and execute it.
--- On Fri, 2/11/11, Roman Chertov <[email protected]> wrote: > > Are you talking about a case in > which you need to set Handler::NONEXCLUSIVE > > for performance reasons? > > Yes, I have an element that emulates an MF-TDMA link, and > the MF-TDMA schedule > can be altered at arbitrary points in time by a user level > process. So ideally, > I would like to be able to install a new schedule, while > continuing to emulate > the link. ____________________________________________________________________________________ Get your own web address. Have a HUGE year through Yahoo! Small Business. http://smallbusiness.yahoo.com/domains/?p=BESTDEAL _______________________________________________ click mailing list [email protected] https://amsterdam.lcs.mit.edu/mailman/listinfo/click
