Commit 17a9e7bbae178d1326e4631ab6350a272349c99d

Authored by Randy Dunlap
Committed by Jens Axboe
1 parent 02e031cbc8

Documentation: remove anticipatory scheduler info

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>
Signed-off-by: Jens Axboe <jaxboe@fusionio.com>

Showing 3 changed files with 7 additions and 7 deletions Side-by-side Diff

Documentation/block/switching-sched.txt
... ... @@ -16,7 +16,7 @@
16 16 As of the Linux 2.6.10 kernel, it is now possible to change the
17 17 IO scheduler for a given block device on the fly (thus making it possible,
18 18 for instance, to set the CFQ scheduler for the system default, but
19   -set a specific device to use the anticipatory or noop schedulers - which
  19 +set a specific device to use the deadline or noop schedulers - which
20 20 can improve that device's throughput).
21 21  
22 22 To set a specific scheduler, simply do this:
23 23  
... ... @@ -31,8 +31,8 @@
31 31 will be displayed, with the currently selected scheduler in brackets:
32 32  
33 33 # cat /sys/block/hda/queue/scheduler
34   -noop anticipatory deadline [cfq]
35   -# echo anticipatory > /sys/block/hda/queue/scheduler
  34 +noop deadline [cfq]
  35 +# echo deadline > /sys/block/hda/queue/scheduler
36 36 # cat /sys/block/hda/queue/scheduler
37   -noop [anticipatory] deadline cfq
  37 +noop [deadline] cfq
Documentation/kernel-parameters.txt
... ... @@ -706,7 +706,7 @@
706 706 arch/x86/kernel/cpu/cpufreq/elanfreq.c.
707 707  
708 708 elevator= [IOSCHED]
709   - Format: {"anticipatory" | "cfq" | "deadline" | "noop"}
  709 + Format: {"cfq" | "deadline" | "noop"}
710 710 See Documentation/block/as-iosched.txt and
711 711 Documentation/block/deadline-iosched.txt for details.
712 712  
Documentation/rbtree.txt
... ... @@ -21,8 +21,8 @@
21 21 To quote Linux Weekly News:
22 22  
23 23 There are a number of red-black trees in use in the kernel.
24   - The anticipatory, deadline, and CFQ I/O schedulers all employ
25   - rbtrees to track requests; the packet CD/DVD driver does the same.
  24 + The deadline and CFQ I/O schedulers employ rbtrees to
  25 + track requests; the packet CD/DVD driver does the same.
26 26 The high-resolution timer code uses an rbtree to organize outstanding
27 27 timer requests. The ext3 filesystem tracks directory entries in a
28 28 red-black tree. Virtual memory areas (VMAs) are tracked with red-black