Re: [2.6 patch] make I/O schedulers non-modular

[Jens Axboe <jens.axboe@oracle.com>]

On Sun, Nov 25 2007, Adrian Bunk wrote:
> On Sun, Nov 25, 2007 at 05:45:32PM +0100, Jens Axboe wrote:
> > On Sun, Nov 25 2007, Adrian Bunk wrote:
> > > On Sun, Nov 25, 2007 at 05:21:07PM +0100, Jens Axboe wrote:
> > > > On Sun, Nov 25 2007, Adrian Bunk wrote:
> > > > > There isn't any big advantage and doesn't seem to be much usage of 
> > > > > modular schedulers.
> > > > > 
> > > > > OTOH, the overhead made the kernel image of an x86 defconfig (that 
> > > > > doesn't use modular schedulers) bigger by nearly 2 kB.
> > > > 
> > > > Big nack, I use it all the time for testing.
> > > 
> > > OK.
> > > 
> > > > Just because you don't
> > > > happen to use it is not a reason to remove it.
> > > 
> > > s/you/you and all distributions you checked/
> > 
> > Well they should make them modules (two of them, that is).
> >...
> 
> Is there any technical reason why we need 4 different schedulers at all?

Until we have the perfect scheduler :-)

With some hard work and testing, we should be able to get rid of 'as'.
It still beats cfq for some of the workloads that deadline is good at,
so not quite yet.

> I have the gut feeling that the usual thing happens and people e.g. not 
> report some cfq problems because as works for them...

There's always a risk with "duplicate", like several drivers for the
same hardware. I'm not disputing that.

-- 
Jens Axboe