Am Samstag, 31. März 2007 04:59 schrieb Alan Stern:
> There still remains the question of how to do this cleanly. Obviously
> some sort of synchronization primitive is needed. wait_for_completion()
> includes all the necessary memory barriers, whereas wait_event() does not.
> Or a spinlock could be used, although it would be somewhat awkward.
wait_event() is very bad in that regard. I'd even call it broken. It should
include memory barriers.
Regards
Oliver
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
