On Mon, 2006-10-30 at 10:16 -0800, Pete Zaitcev wrote: > I am looking forward to your agreement about the master API structure > as I outlined (yes, without the next_urb field for now).
This design is ok for me. I'm sorry for a possibly dumb question, but I have some trouble to understand the issue with the 'next_urb' field. I thought that this field could be used as the way to synchronize the user space with the kernel. A marker could be used to specify 'No other urb available'. The user space can use select to wait for any data, or can do polling on the next_urb field. When any data is ready, the user app can walk the circular buffer, using the next_urb field and processing the found urbs, until it meet a 'No next header available' mark. Are there any issues with cache memory and/or out-of-order memory access?!? If so, could this problems be fixed with some kind of memory barrier implemented into the driver after writing the urb header?!? ciao, Paolo ------------------------------------------------------------------------- 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
