PageRenderTime 7ms CodeModel.GetById 2ms app.highlight 1ms RepoModel.GetById 2ms app.codeStats 0ms

Unknown | 41 lines | 35 code | 6 blank | 0 comment | 0 complexity | 4827712a752d4520e94ba03915524c6c MD5 | raw file
 2menu "IO Schedulers"
 5	bool
 6	default y
 7	---help---
 8	  The no-op I/O scheduler is a minimal scheduler that does basic merging
 9	  and sorting. Its main uses include non-disk based block devices like
10	  memory devices, and specialised software or hardware environments
11	  that do their own scheduling and require only minimal assistance from
12	  the kernel.
14config IOSCHED_AS
15	tristate "Anticipatory I/O scheduler"
16	default y
17	---help---
18	  The anticipatory I/O scheduler is the default disk scheduler. It is
19	  generally a good choice for most environments, but is quite large and
20	  complex when compared to the deadline I/O scheduler, it can also be
21	  slower in some cases especially some database loads.
24	tristate "Deadline I/O scheduler"
25	default y
26	---help---
27	  The deadline I/O scheduler is simple and compact, and is often as
28	  good as the anticipatory I/O scheduler, and in some database
29	  workloads, better. In the case of a single process performing I/O to
30	  a disk at any one time, its behaviour is almost identical to the
31	  anticipatory I/O scheduler and so is a good choice.
33config IOSCHED_CFQ
34	tristate "CFQ I/O scheduler"
35	default y
36	---help---
37	  The CFQ I/O scheduler tries to distribute bandwidth equally
38	  among all processes in the system. It should provide a fair
39	  working environment, suitable for desktop systems.