Yes
> At least historically that's a major mistake, and generates a crappy
> elevator, because it removes information from the block layer about where
> the disk is (or is going to be).
Not necessarily, the io schedulers keep track of where we are going. You
don't need an active front request for that.
> I know Andrew thinks that SCSI tagged queuing is a bunch of crap, and he
> has the latency numbers to prove it. He blames the SCSI disks themselves,
> but I think it might be the fact that SCSI makes it impossible to make a
> fair queuing algorithm for higher levels by hiding information.
>
> Has anybody looked at just removing the request at command _completion_
> time instead? That's what IDE does, and it's the _right_ thing to do.
I know this is a pet peeve of yours (must be, I remember you bringing it
up at least 3 time before :), but I don't think that's necessarily true.
It shouldn't matter _one_ bit whether you leave the request there or
not, it's unmergeable. As long as the io scheduler keeps track of this
(and it does!) we are golden.
-- Jens Axboe- 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/