Sergei Shtylyov wrote:
Handling of the trailing byte in ata_sff_data_xfer() is suboptimal bacause:
- it always initializes the padding buffer to 0 which is not really needed in
both the read and write cases;
- it has to use memcpy() to transfer a single byte from/to the padding buffer;
Have you looked at the assembly, before deciding it is suboptiomal?
gcc optimizes tiny arrays and structures quite well, and is well capable
of seeing one path where the initialization is clobbered without a
single read, and another code path where it is used.
As for memcpy, for small and/or constant values that is quite often a
compiler builtin. It is rarely useful, these days, to convert a
memcpy() to a hand-rolled version of same.
Jeff
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
