Messages in this thread | | | Date | Mon, 19 Feb 2001 02:02:19 +0000 (GMT) | From | Alan Cox <> |
| |
> > But it has to go somewhere, and 2.4 right now is unusable on two of my boxes > > with M/O drives. > > Reads can be pretty easily padded, but writes are a bit harder. Maybe > push it to some helper before the device queue sees it? For 2.4 the > best sd solution is probably to just make it able to handle these > requests.
For M/O drives you can do it in the scsi layer. Doing it right in the block layer is not easy. Doing it cleanly and right I cant currently visualise a setu for. But I agree it belongs in the queueing layers
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |