On Wed, Aug 12, 2015 at 12:12:30PM +0200, Markus Pargmann wrote: > Currently we try to write the data without copying directly using > bus->write() or bus->gather_write() if it exists. If one of the previous > tries to write reported -ENOTSUPP or none of them were usable, we copy > the data into a buffer and use bus->write(). > > However it does not make sense to try bus->write() a second time with a > copied buffer if it didn't work the first time. > > This patch restructures this if/else block to make it clear that this is > not intended for the case where bus->write() returns -ENOTSUPP. I'm not entirely convinced that this is an improvement. The main effect that I'm seeing is an increase in the indentation level and there are potential issues with the write operation being unable to work with some kinds of memory (like restrictions about dmaing from stack or unalinged memory for example) which mean that copying into a newly allocated buffer may actually help. I don't think we detect any such restrictions at the minute but the defensiveness is nice and I'd really hope that the failed write case isn't any kind of fast path.
Attachment:
signature.asc
Description: Digital signature
