LKML Archive on
help / color / mirror / Atom feed
From: "Rogério Brito" <>
Subject: [PATCH] trivial: fix documentation regarding default io scheduler
Date: Sun, 19 Oct 2008 05:24:21 -0200	[thread overview]
Message-ID: <> (raw)

The current Kconfig.iosched documentation says that the default I/O
scheduler is the CFQ scheduler, but the default, if nothing is changed,
is the anticipatory scheduler.

This patch fixes the documentation.

Signed-off-by: Rogério Brito <>


--- linux/block/Kconfig.iosched.old
+++ linux/block/Kconfig.iosched
@@ -19,7 +19,7 @@
 	  The anticipatory I/O scheduler is generally a good choice for most
 	  environments, but is quite large and complex when compared to the
 	  deadline I/O scheduler, it can also be slower in some cases
-	  especially some database loads.
+	  especially some database loads.  This is the default I/O scheduler.
 	tristate "Deadline I/O scheduler"
@@ -38,7 +38,6 @@
 	  The CFQ I/O scheduler tries to distribute bandwidth equally
 	  among all processes in the system. It should provide a fair
 	  working environment, suitable for desktop systems.
-	  This is the default I/O scheduler.
 	prompt "Default I/O scheduler"

Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8 :
Projects: : :

             reply	other threads:[~2008-10-19  7:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-19  7:24 Rogério Brito [this message]
2008-10-19 15:41 ` Jonathan Corbet

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: [PATCH] trivial: fix documentation regarding default io scheduler' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).