Linux-2.6.12-rc2v2.6.12-rc2

Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.

Let it rip!

1 files changed, 41 insertions, 0 deletions

diff --git a/drivers/block/Kconfig.iosched b/drivers/block/Kconfig.iosched
new file mode 100644
index 000000000000..6070a480600b
--- /dev/null
+++ b/drivers/block/Kconfig.iosched
@@ -0,0 +1,41 @@
+
+menu "IO Schedulers"
+
+config IOSCHED_NOOP
+        bool
+        default y
+        ---help---
+          The no-op I/O scheduler is a minimal scheduler that does basic merging
+          and sorting. Its main uses include non-disk based block devices like
+          memory devices, and specialised software or hardware environments
+          that do their own scheduling and require only minimal assistance from
+          the kernel.
+
+config IOSCHED_AS
+        tristate "Anticipatory I/O scheduler"
+        default y
+        ---help---
+          The anticipatory I/O scheduler is the default disk scheduler. It 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.
+
+config IOSCHED_DEADLINE
+        tristate "Deadline I/O scheduler"
+        default y
+        ---help---
+          The deadline I/O scheduler is simple and compact, and is often as
+          good as the anticipatory I/O scheduler, and in some database
+          workloads, better. In the case of a single process performing I/O to
+          a disk at any one time, its behaviour is almost identical to the
+          anticipatory I/O scheduler and so is a good choice.
+
+config IOSCHED_CFQ
+        tristate "CFQ I/O scheduler"
+        default y
+        ---help---
+          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.
+
+endmenu