Re: performance "regression" in cfq compared to anticipatory, deadline and noop

From: Fabio Checconi
Date: Fri May 16 2008 - 03:40:33 EST

> From: Jens Axboe <jens.axboe@xxxxxxxxxx>
> Date: Fri, May 16, 2008 08:40:03AM +0200
> I think we can improve this further without getting too involved. If a
> 2nd request is seen in cfq_rq_enqueued(), then DO schedule a dispatch
> since this likely means that we wont be doing more merges on the first
> one.

But isn't there the risk that even the second request would be
dispatched, while it still could have grown?

Moreover I am still unsure about how to handle (and if it's worth
handling) the case in which we restart queueing after an empty
dispatch round due to idling, as it would still have the same

(Also anticipatory doesn't handle this case too well.)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at