On Thu, Apr 08, 2010 at 04:09:44PM +0200, Jens Axboe wrote: [..] > Precisely. The next question would be how to control the yielding. In > this particular case, you want to be yielding to a specific cfqq. IOW, > you essentially want to pass your slide on to that queue. The way the > above is implemented, you could easily just switch to another unrelated > queue. And if that is done, fairness is skewed without helping the > yielding process at all (which was the intention). > True. I guess this is relatively simple yield implementation where we are telling IO scheduler that there is no more IO coming on this context so don't waste time idling. That's a different thing that after giving up slice, cfq might schedule in another sequential reader instead of journalling thread. Ideally it would be better to be also able to specify who to transfer remaining slice to. I am not sure if there is an easy way to pass this info CFQ. So this implementation might be good first step. Vivek -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
