[PATCH] BLOCK: Make it possible to disable the block layer [try #6]
Make it possible to disable the block layer. Not all embedded devices require
it, some can make do with just JFFS2, NFS, ramfs, etc - none of which require
the block layer to be present.
This patch does the following:
(*) Introduces CONFIG_BLOCK to disable the block layer, buffering and blockdev
support.
(*) Adds dependencies on CONFIG_BLOCK to any configuration item that controls
an item that uses the block layer. This includes:
(*) Block I/O tracing.
(*) Disk partition code.
(*) All filesystems that are block based, eg: Ext3, ReiserFS, ISOFS.
(*) The SCSI layer. As far as I can tell, even SCSI chardevs use the
block layer to do scheduling. Some drivers that use SCSI facilities -
such as USB storage - end up disabled indirectly from this.
(*) Various block-based device drivers, such as IDE and the old CDROM
drivers.
(*) MTD blockdev handling and FTL.
(*) JFFS - which uses set_bdev_super(), something it could avoid doing by
taking a leaf out of JFFS2's book.
(*) Makes most of the contents of linux/blkdev.h, linux/buffer_head.h and
linux/elevator.h contingent on CONFIG_BLOCK being set. sector_div() is,
however, still used in places, and so is still available.
(*) Also made contingent are the contents of linux/mpage.h, linux/genhd.h and
parts of linux/fs.h.
(*) Makes a number of files in fs/ contingent on CONFIG_BLOCK.
(*) Makes mm/bounce.c (bounce buffering) contingent on CONFIG_BLOCK.
(*) set_page_dirty() doesn't call __set_page_dirty_buffers() if CONFIG_BLOCK
is not enabled.
(*) fs/no-block.c is created to hold out-of-line stubs and things that are
required when CONFIG_BLOCK is not set:
(*) Default blockdev file operations (to give error ENODEV on opening).
(*) Makes some /proc changes:
(*) /proc/devices does not list any blockdevs.
(*) /proc/diskstats and /proc/partitions are contingent on CONFIG_BLOCK.
(*) Makes some compat ioctl handling contingent on CONFIG_BLOCK.
(*) If CONFIG_BLOCK is not defined, makes sys_quotactl() return -ENODEV if
given command other than Q_SYNC or if a special device is specified.
(*) In init/do_mounts.c, no reference is made to the blockdev routines if
CONFIG_BLOCK is not defined. This does not prohibit NFS roots or JFFS2.
(*) The bdflush, ioprio_set and ioprio_get syscalls can now be absent (return
error ENOSYS by way of cond_syscall if so).
(*) The seclvl_bd_claim() and seclvl_bd_release() security calls do nothing if
CONFIG_BLOCK is not set, since they can't then happen.
Signed-Off-By: David Howells <dhowells@redhat.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
19 years ago
|
|
|
if BLOCK
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
choice
|
|
|
|
|
prompt "Default I/O scheduler"
|
|
|
|
|
default DEFAULT_CFQ
|
|
|
|
|
help
|
|
|
|
|
Select the I/O scheduler which will be used by default for all
|
|
|
|
|
block devices.
|
|
|
|
|
|
|
|
|
|
config DEFAULT_AS
|
|
|
|
|
bool "Anticipatory" if IOSCHED_AS=y
|
|
|
|
|
|
|
|
|
|
config DEFAULT_DEADLINE
|
|
|
|
|
bool "Deadline" if IOSCHED_DEADLINE=y
|
|
|
|
|
|
|
|
|
|
config DEFAULT_CFQ
|
|
|
|
|
bool "CFQ" if IOSCHED_CFQ=y
|
|
|
|
|
|
|
|
|
|
config DEFAULT_NOOP
|
|
|
|
|
bool "No-op"
|
|
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
|
|
|
|
config DEFAULT_IOSCHED
|
|
|
|
|
string
|
|
|
|
|
default "anticipatory" if DEFAULT_AS
|
|
|
|
|
default "deadline" if DEFAULT_DEADLINE
|
|
|
|
|
default "cfq" if DEFAULT_CFQ
|
|
|
|
|
default "noop" if DEFAULT_NOOP
|
|
|
|
|
|
|
|
|
|
endmenu
|
[PATCH] BLOCK: Make it possible to disable the block layer [try #6]
Make it possible to disable the block layer. Not all embedded devices require
it, some can make do with just JFFS2, NFS, ramfs, etc - none of which require
the block layer to be present.
This patch does the following:
(*) Introduces CONFIG_BLOCK to disable the block layer, buffering and blockdev
support.
(*) Adds dependencies on CONFIG_BLOCK to any configuration item that controls
an item that uses the block layer. This includes:
(*) Block I/O tracing.
(*) Disk partition code.
(*) All filesystems that are block based, eg: Ext3, ReiserFS, ISOFS.
(*) The SCSI layer. As far as I can tell, even SCSI chardevs use the
block layer to do scheduling. Some drivers that use SCSI facilities -
such as USB storage - end up disabled indirectly from this.
(*) Various block-based device drivers, such as IDE and the old CDROM
drivers.
(*) MTD blockdev handling and FTL.
(*) JFFS - which uses set_bdev_super(), something it could avoid doing by
taking a leaf out of JFFS2's book.
(*) Makes most of the contents of linux/blkdev.h, linux/buffer_head.h and
linux/elevator.h contingent on CONFIG_BLOCK being set. sector_div() is,
however, still used in places, and so is still available.
(*) Also made contingent are the contents of linux/mpage.h, linux/genhd.h and
parts of linux/fs.h.
(*) Makes a number of files in fs/ contingent on CONFIG_BLOCK.
(*) Makes mm/bounce.c (bounce buffering) contingent on CONFIG_BLOCK.
(*) set_page_dirty() doesn't call __set_page_dirty_buffers() if CONFIG_BLOCK
is not enabled.
(*) fs/no-block.c is created to hold out-of-line stubs and things that are
required when CONFIG_BLOCK is not set:
(*) Default blockdev file operations (to give error ENODEV on opening).
(*) Makes some /proc changes:
(*) /proc/devices does not list any blockdevs.
(*) /proc/diskstats and /proc/partitions are contingent on CONFIG_BLOCK.
(*) Makes some compat ioctl handling contingent on CONFIG_BLOCK.
(*) If CONFIG_BLOCK is not defined, makes sys_quotactl() return -ENODEV if
given command other than Q_SYNC or if a special device is specified.
(*) In init/do_mounts.c, no reference is made to the blockdev routines if
CONFIG_BLOCK is not defined. This does not prohibit NFS roots or JFFS2.
(*) The bdflush, ioprio_set and ioprio_get syscalls can now be absent (return
error ENOSYS by way of cond_syscall if so).
(*) The seclvl_bd_claim() and seclvl_bd_release() security calls do nothing if
CONFIG_BLOCK is not set, since they can't then happen.
Signed-Off-By: David Howells <dhowells@redhat.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
19 years ago
|
|
|
|
|
|
|
|
endif
|
