> So put 0 and sure anyone can submit I/O on the size that they want.
> Now the driver has to support padding reads, or gathering data to do
> a complete block write. This is silly. Sr should support 512b transfers
> just fine, but only because I added the necessary _hacks_ to support
> it. sd doesn't right now for instance.
It is silly to be in the block layer, it is silly to be in each file system.
Perhaps it belongs in the block queueing/handling code or the caches
But it has to go somewhere, and 2.4 right now is unusable on two of my boxes
with M/O drives.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
