From: "Paa Paa" <paapaa125@hotmail.com>
To: linux-kernel@vger.kernel.org
Subject: CFQ will be the new default IO scheduler - why?
Date: Sun, 23 Jul 2006 19:08:17 +0000 [thread overview]
Message-ID: <BAY20-F21F536F116290D1C8F5FF4F9640@phx.gbl> (raw)
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.
What is the reason CFQ will be the new default? What advantages it has over
AS performance and feature wise? Any links to relevant and recent
benchmarks?
And if there is a recent discussion about this online, a link would be
greatly appreciated.
Best regards,
Paapaa
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
next reply other threads:[~2006-07-23 19:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-23 19:08 Paa Paa [this message]
2006-07-24 8:29 ` Matthias Andree
2006-07-24 12:41 ` Justin Piszcz
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=BAY20-F21F536F116290D1C8F5FF4F9640@phx.gbl \
--to=paapaa125@hotmail.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®