aboutsummaryrefslogtreecommitdiffstats
path: root/block/Kconfig.iosched
diff options
context:
space:
mode:
authorJens Axboe <jens.axboe@oracle.com>2009-10-03 03:37:51 -0400
committerJens Axboe <jens.axboe@oracle.com>2009-10-03 03:37:51 -0400
commit492af6350a5ccf087e4964104a276ed358811458 (patch)
tree81d6398597758f5b712e1f47a3f24f0da66127ba /block/Kconfig.iosched
parent6a0afdf58d40200abd0c717261d1bc4c49195c2f (diff)
block: remove the anticipatory IO scheduler
AS is mostly a subset of CFQ, so there's little point in still providing this separate IO scheduler. Hopefully at some point we can get down to one single IO scheduler again, at least this brings us closer by having only one intelligent IO scheduler. Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
Diffstat (limited to 'block/Kconfig.iosched')
-rw-r--r--block/Kconfig.iosched22
1 files changed, 4 insertions, 18 deletions
diff --git a/block/Kconfig.iosched b/block/Kconfig.iosched
index 7e803fc88770..baad3dae3655 100644
--- a/block/Kconfig.iosched
+++ b/block/Kconfig.iosched
@@ -12,24 +12,14 @@ config IOSCHED_NOOP
12 that do their own scheduling and require only minimal assistance from 12 that do their own scheduling and require only minimal assistance from
13 the kernel. 13 the kernel.
14 14
15config IOSCHED_AS
16 tristate "Anticipatory I/O scheduler"
17 default y
18 ---help---
19 The anticipatory I/O scheduler is generally a good choice for most
20 environments, but is quite large and complex when compared to the
21 deadline I/O scheduler, it can also be slower in some cases
22 especially some database loads.
23
24config IOSCHED_DEADLINE 15config IOSCHED_DEADLINE
25 tristate "Deadline I/O scheduler" 16 tristate "Deadline I/O scheduler"
26 default y 17 default y
27 ---help--- 18 ---help---
28 The deadline I/O scheduler is simple and compact, and is often as 19 The deadline I/O scheduler is simple and compact. It will provide
29 good as the anticipatory I/O scheduler, and in some database 20 CSCAN service with FIFO expiration of requests, switching to
30 workloads, better. In the case of a single process performing I/O to 21 a new point in the service tree and doing a batch of IO from there
31 a disk at any one time, its behaviour is almost identical to the 22 in case of expiry.
32 anticipatory I/O scheduler and so is a good choice.
33 23
34config IOSCHED_CFQ 24config IOSCHED_CFQ
35 tristate "CFQ I/O scheduler" 25 tristate "CFQ I/O scheduler"
@@ -47,9 +37,6 @@ choice
47 Select the I/O scheduler which will be used by default for all 37 Select the I/O scheduler which will be used by default for all
48 block devices. 38 block devices.
49 39
50 config DEFAULT_AS
51 bool "Anticipatory" if IOSCHED_AS=y
52
53 config DEFAULT_DEADLINE 40 config DEFAULT_DEADLINE
54 bool "Deadline" if IOSCHED_DEADLINE=y 41 bool "Deadline" if IOSCHED_DEADLINE=y
55 42
@@ -63,7 +50,6 @@ endchoice
63 50
64config DEFAULT_IOSCHED 51config DEFAULT_IOSCHED
65 string 52 string
66 default "anticipatory" if DEFAULT_AS
67 default "deadline" if DEFAULT_DEADLINE 53 default "deadline" if DEFAULT_DEADLINE
68 default "cfq" if DEFAULT_CFQ 54 default "cfq" if DEFAULT_CFQ
69 default "noop" if DEFAULT_NOOP 55 default "noop" if DEFAULT_NOOP