Yeah, but some manufacturers are good enough to put it in the tech notes.
Should the scheduling algo be put in as a device strategy function, with
fallback to the current elevator if the device doesnt have one? Then we could
implement two way elevator algos for those hard disks for which we can get
physical geometry info from the data sheets or somewhere.
And another probably dumb question which should be answered by rtfs, but here
goes anyway:
what happens for devices like ramdisks or loopback devices etc for which
scheduling in random order is ok anyway?
-- arvind
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/