From: Al Boldi <a1426z@gawab.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Adrian Bunk <bunk@stusta.de>,
Jens Axboe <jens.axboe@oracle.com>
Subject: Re: [2.6 patch] make I/O schedulers non-modular
Date: Mon, 26 Nov 2007 08:28:41 +0300 [thread overview]
Message-ID: <200711260828.41021.a1426z@gawab.com> (raw)
In-Reply-To: <20071125211259.c69040fa.akpm@linux-foundation.org>
Andrew Morton wrote:
> (cc's lovingly restored. Please do not do that)
Thanks! I'm replying off list.
> On Mon, 26 Nov 2007 07:57:00 +0300 Al Boldi <a1426z@gawab.com> wrote:
> > Jens Axboe wrote:
> > > On Sun, Nov 25 2007, Adrian Bunk wrote:
> > > > 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.
> >
> > Actually, both 'cfq' and 'as' are broken, and have been repeatedly
> > reported as such. Deadline is the only one that currently looks sane,
> > and seems like a good starting point for a more involved iosched. But
> > keep in mind, the fact that 'cfq' and 'as' are broken may also point to
> > a lower-level block-io problem. So, incrementally improving deadline
> > may help discovering the problems both 'cfq' and 'as' are plagued with.
>
> Sorry, but these are vague and unuseful assertions.
>
> Please send bug reports, preferably with testcases which developers can
> use when fixing the bugs.
http://bugzilla.kernel.org/show_bug.cgi?id=5900
Thanks again!
--
Al
next prev parent reply other threads:[~2007-11-26 5:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-25 16:18 Adrian Bunk
2007-11-25 16:21 ` Jens Axboe
2007-11-25 16:31 ` Adrian Bunk
2007-11-25 16:45 ` Jens Axboe
2007-11-25 16:56 ` Adrian Bunk
2007-11-25 17:22 ` Jens Axboe
2007-11-26 4:57 ` Al Boldi
2007-11-26 5:12 ` Andrew Morton
2007-11-26 5:28 ` Al Boldi [this message]
2007-11-27 7:09 ` Jarek Poplawski
2007-11-27 16:47 ` Adrian Bunk
2007-11-27 22:15 ` Jarek Poplawski
2007-11-27 22:53 ` Adrian Bunk
2007-11-28 0:20 ` Jarek Poplawski
2007-11-27 23:02 ` Jarek Poplawski
2007-11-27 23:21 ` Adrian Bunk
2007-12-30 17:52 ` Jarek Poplawski
2007-11-25 23:27 ` Arjan van de Ven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200711260828.41021.a1426z@gawab.com \
--to=a1426z@gawab.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@stusta.de \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®