public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: linux-kernel@vger.kernel.org
Cc: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Jens Axboe <axboe@kernel.dk>
Subject: [PATCH 7/8] Documentation: remove anticipatory scheduler info
Date: Wed, 10 Nov 2010 11:53:50 -0800	[thread overview]
Message-ID: <12894188301171@xenotime.net> (raw)
In-Reply-To: <1289418830794@xenotime.net>

From: Randy Dunlap <randy.dunlap@oracle.com>

Remove anticipatory block I/O scheduler info from Documentation/
since the code has been deleted.

Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Reported-by: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Jens Axboe <axboe@kernel.dk>
---
 Documentation/block/switching-sched.txt |    8 ++++----
 Documentation/kernel-parameters.txt     |    2 +-
 Documentation/rbtree.txt                |    4 ++--
 3 files changed, 7 insertions(+), 7 deletions(-)

--- linux-2.6.37-rc1-git8.orig/Documentation/block/switching-sched.txt
+++ linux-2.6.37-rc1-git8/Documentation/block/switching-sched.txt
@@ -16,7 +16,7 @@ you can do so by typing:
 As of the Linux 2.6.10 kernel, it is now possible to change the
 IO scheduler for a given block device on the fly (thus making it possible,
 for instance, to set the CFQ scheduler for the system default, but
-set a specific device to use the anticipatory or noop schedulers - which
+set a specific device to use the deadline or noop schedulers - which
 can improve that device's throughput).
 
 To set a specific scheduler, simply do this:
@@ -31,7 +31,7 @@ a "cat /sys/block/DEV/queue/scheduler" -
 will be displayed, with the currently selected scheduler in brackets:
 
 # cat /sys/block/hda/queue/scheduler
-noop anticipatory deadline [cfq]
-# echo anticipatory > /sys/block/hda/queue/scheduler
+noop deadline [cfq]
+# echo deadline > /sys/block/hda/queue/scheduler
 # cat /sys/block/hda/queue/scheduler
-noop [anticipatory] deadline cfq
+noop [deadline] cfq
--- linux-2.6.37-rc1-git8.orig/Documentation/kernel-parameters.txt
+++ linux-2.6.37-rc1-git8/Documentation/kernel-parameters.txt
@@ -706,7 +706,7 @@ and is between 256 and 4096 characters. 
 			arch/x86/kernel/cpu/cpufreq/elanfreq.c.
 
 	elevator=	[IOSCHED]
-			Format: {"anticipatory" | "cfq" | "deadline" | "noop"}
+			Format: {"cfq" | "deadline" | "noop"}
 			See Documentation/block/as-iosched.txt and
 			Documentation/block/deadline-iosched.txt for details.
 
--- linux-2.6.37-rc1-git8.orig/Documentation/rbtree.txt
+++ linux-2.6.37-rc1-git8/Documentation/rbtree.txt
@@ -21,8 +21,8 @@ three rotations, respectively, to balanc
 To quote Linux Weekly News:
 
     There are a number of red-black trees in use in the kernel.
-    The anticipatory, deadline, and CFQ I/O schedulers all employ
-    rbtrees to track requests; the packet CD/DVD driver does the same.
+    The deadline and CFQ I/O schedulers employ rbtrees to
+    track requests; the packet CD/DVD driver does the same.
     The high-resolution timer code uses an rbtree to organize outstanding
     timer requests.  The ext3 filesystem tracks directory entries in a
     red-black tree.  Virtual memory areas (VMAs) are tracked with red-black


-- 


  parent reply	other threads:[~2010-11-10 22:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-10 19:53 [for review: PATCH 1/8] kernel-doc: escape xml for structs Randy Dunlap
2010-11-10 19:53 ` [PATCH 6/8] Documentation/development-process: more staging info Randy Dunlap
2010-11-10 19:53 ` [PATCH 8/8] MAINTAINERS: update documentation entries Randy Dunlap
2010-11-10 19:53 ` [PATCH 4/8] Documentation: change email address for Hans Koch Randy Dunlap
2010-11-10 19:53 ` [PATCH 2/8] Documentation: make configfs example code simpler, clearer Randy Dunlap
2010-11-10 19:53 ` [PATCH 3/8] Documentation/gpio.txt: explain poll/select usage Randy Dunlap
2010-11-10 19:53 ` Randy Dunlap [this message]
2010-11-11 11:10   ` [PATCH 7/8] Documentation: remove anticipatory scheduler info Jens Axboe
2010-11-10 19:53 ` [PATCH 5/8] Documentation/development-process: use -next trees instead of staging Randy Dunlap

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=12894188301171@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpjday@crashcourse.ca \
    /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