Date: Sun, 25 Nov 2007 17:56:54 +0100
From: Adrian Bunk <bunk@kernel.org>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] make I/O schedulers non-modular
Message-ID: <20071125165654.GE21947@stusta.de>
References: <20071125161801.GB21947@stusta.de> <20071125162105.GA6658@kernel.dk> <20071125163153.GD21947@stusta.de> <20071125164532.GB6658@kernel.dk>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20071125164532.GB6658@kernel.dk>
User-Agent: Mutt/1.5.17 (2007-11-01)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1463
Lines: 44

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?

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

> Jens Axboe

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

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