Jens Axboe wrote:
quoted text
> I was thinking about that too. Generally I've been opposed to doing
> scheduling decisions on anything but time, since that is always
> relevant. When to hand out slices and to what process, that algorithm is
> really basic in CFQ and could do with an improvement.
>   

Jumping in at random, does "process" here mean task or mms_struct?  If 
the former, doesn't that mean that a 100-thread process can starve out a 
single-threaded process?

Perhaps we need hierarchical io scheduling, like cfs has for the cpu.

-- 
error compiling committee.c: too many arguments to function

--
unsubscribe notice
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/