Alan Cox wrote:
Yeah, that has long been a design decision -- avoid all the mechanics of
PIO-Multi, simply because we did not have much of a need for it (and
still don't).
Albert Lee worked on PIO-Multi a while ago, which was mainly to get
ATA_{12,16} working, IIRC.
But overall, I don't see much of a need to introduce it into the main stack?
I don't see a need - and if we do its more important IMHO to get the PIO
paths out of the irq handlers before doing so.
..
That's not a new concern, given that we *already* perform multi-sector I/O.
And it's not really related to improving the implementation to be better
aware of multi-sector I/O and interaction with EH.
But yeah, a good thing nonetheless.
Cheers
--
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
