> > The simple way to meet Badari's current goal is: calculate the length > > of the whole iovec, use that to allocate the right size i/o buffer, then > > have the AIO write path gather data into that, and the AIO read "retry" > > path scatter data out of it after reads complete. > > Okay. That sounds like the kind of thing that should already be written > somewhere. If not, it should be added in some central place where other > drivers can use it too.
In the block layer somewhere, I'd guess. > > Then there'd be the asymmetry that IN endpoints can be halted using read() > > but not with readv() -- similarly for OUT and write() -- but that's a very > > livable issue. > > You mean with a "wrong-direction" I/O call? Why can't that be done with > readv/writev? Especially if the total transfer length is zero? Because of the way the code sharing is structured; that's just continuing the current restriction. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&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
