On 6 feb 2007, at 13:18, Oliver Neukum wrote: >>> And 'volatile' in C have nothing to do with hardware: SMP, caches or >>> whatever there may be. >> >> The problem that we're trying to solve has not much to do with >> hardware. I'd like to solve it at a pure logical level: by using some >> interface that guarantees certain ordering constraints. I prefer not >> to > > "volatile" doesn't. It just implies a compiler constraint. It is pretty > useless.
Yeah, I understand that now, just found the "remove volatile" lkml thread. At first I though that atomic_t would do the trick, but apparently it doesn't. So spinlocks it is then, because I don't feel ready to play with memory barriers. Thanks for the pointers, Joris. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
