Mark Lord wrote:
Jeff Garzik wrote:
Once the sysfs attr's actually work, I'll probably re-do my hdparm
stuff to detect use them when available, avoiding the need for libata
to snoop passthrough commands. But Jeff may (or not) want to snoop
anyway.
We _have_ to snoop some commands, like SET FEATURES - XFER MODE.
Its just a given... you gotta either maintain cached state, or you
gotta notice when its stale.
Ah then, I suppose libata might as well snoop the write-cache on/off
(SET FEATURES) command as well. We need some kind of API or something
to avoid the nasty layering violation that my hack uses.. I wonder if
we can just do a revalidate disk or something?
Either way. Revalidation falls under the "notice when its stale"
category above, certainly a viable solution.
Jeff
-
: 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
