From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Matthias Andree <matthias.andree@gmx.de>
Cc: Paa Paa <paapaa125@hotmail.com>, linux-kernel@vger.kernel.org
Subject: Re: CFQ will be the new default IO scheduler - why?
Date: Mon, 24 Jul 2006 08:41:37 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0607240840560.1094@p34.internal.lan> (raw)
In-Reply-To: <20060724082916.GB24299@merlin.emma.line.org>
On Mon, 24 Jul 2006, Matthias Andree wrote:
> On Sun, 23 Jul 2006, Paa Paa wrote:
>
>> The default IO scheduler in 2.6.18 will be CFQ (Complete Fair Queuing)
>> instead of AS (Anticipatory Scheduler) as described here:
>> http://wiki.kernelnewbies.org/Linux_2_6_18. I tried to find (here, at lkml)
>> the discussion about this change with no luck.
>
> That wiki document nicely shows the advantage of the scheduler, namely
> that you have "ionice", which isn't possible for AS or Deadline
> Schedulers - this allows the operating system to run processes like
> updatedb with "nice I/O", meaning these hold when you're doing other
> I/O.
>
> --
> Matthias Andree
> -
> 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/
>
Should there be a default scheduler per filesystem? As some filesystems
may perform better/worse with one over another?
Justin.
next prev parent reply other threads:[~2006-07-24 12:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-23 19:08 CFQ will be the new default IO scheduler - why? Paa Paa
2006-07-24 8:29 ` Matthias Andree
2006-07-24 12:41 ` Justin Piszcz [this message]
2006-07-24 15:57 Al Boldi
2006-07-24 16:33 ` Arjan van de Ven
2006-07-25 4:56 ` Al Boldi
2006-07-25 4:59 ` Arjan van de Ven
2006-07-25 18:27 ` Al Boldi
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=Pine.LNX.4.64.0607240840560.1094@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.andree@gmx.de \
--cc=paapaa125@hotmail.com \
/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;
as well as URLs for NNTP newsgroup(s).