2005-11-04 15:43:35 +08:00
|
|
|
#
|
|
|
|
|
# Block layer core configuration
|
|
|
|
|
#
|
2007-07-10 18:24:11 +08:00
|
|
|
menuconfig BLOCK
|
2006-10-01 03:14:05 +08:00
|
|
|
bool "Enable the block layer" if EMBEDDED
|
[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>
2006-10-01 02:45:40 +08:00
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
This permits the block layer to be removed from the kernel if it's not
|
|
|
|
|
needed (on some embedded devices for example). If this option is
|
|
|
|
|
disabled, then blockdev files will become unusable and some
|
|
|
|
|
filesystems (such as ext3) will become unavailable.
|
|
|
|
|
|
|
|
|
|
This option will also disable SCSI character devices and USB storage
|
|
|
|
|
since they make use of various block layer definitions and
|
|
|
|
|
facilities.
|
|
|
|
|
|
|
|
|
|
Say Y here unless you know you really don't want to mount disks and
|
|
|
|
|
suchlike.
|
|
|
|
|
|
|
|
|
|
if BLOCK
|
|
|
|
|
|
2005-11-04 15:43:35 +08:00
|
|
|
config LBD
|
|
|
|
|
bool "Support for Large Block Devices"
|
2006-12-04 18:38:31 +08:00
|
|
|
depends on !64BIT
|
2005-11-04 15:43:35 +08:00
|
|
|
help
|
|
|
|
|
Say Y here if you want to attach large (bigger than 2TB) discs to
|
|
|
|
|
your machine, or if you want to have a raid or loopback device
|
|
|
|
|
bigger than 2TB. Otherwise say N.
|
|
|
|
|
|
2006-03-24 03:00:26 +08:00
|
|
|
config BLK_DEV_IO_TRACE
|
|
|
|
|
bool "Support for tracing block io actions"
|
2006-03-26 20:32:09 +08:00
|
|
|
depends on SYSFS
|
2006-03-24 03:00:26 +08:00
|
|
|
select RELAY
|
|
|
|
|
select DEBUG_FS
|
|
|
|
|
help
|
|
|
|
|
Say Y here, if you want to be able to trace the block layer actions
|
|
|
|
|
on a given queue. Tracing allows you to see any traffic happening
|
|
|
|
|
on a block device queue. For more information (and the user space
|
|
|
|
|
support tools needed), fetch the blktrace app from:
|
|
|
|
|
|
|
|
|
|
git://brick.kernel.dk/data/git/blktrace.git
|
|
|
|
|
|
2006-03-26 17:37:52 +08:00
|
|
|
config LSF
|
|
|
|
|
bool "Support for Large Single Files"
|
2006-12-04 18:38:31 +08:00
|
|
|
depends on !64BIT
|
2006-03-26 17:37:52 +08:00
|
|
|
help
|
2006-03-31 18:30:46 +08:00
|
|
|
Say Y here if you want to be able to handle very large files (bigger
|
|
|
|
|
than 2TB), otherwise say N.
|
|
|
|
|
|
|
|
|
|
If unsure, say Y.
|
2006-03-26 17:37:52 +08:00
|
|
|
|
2007-07-09 18:38:05 +08:00
|
|
|
config BLK_DEV_BSG
|
2007-07-17 18:22:09 +08:00
|
|
|
bool "Block layer SG support v4 (EXPERIMENTAL)"
|
2007-07-19 23:15:10 +08:00
|
|
|
depends on EXPERIMENTAL
|
2007-07-09 18:38:05 +08:00
|
|
|
---help---
|
2007-07-17 18:22:09 +08:00
|
|
|
Saying Y here will enable generic SG (SCSI generic) v4 support
|
|
|
|
|
for any block device.
|
|
|
|
|
|
|
|
|
|
Unlike SG v3 (aka block/scsi_ioctl.c drivers/scsi/sg.c), SG v4
|
|
|
|
|
can handle complicated SCSI commands: tagged variable length cdbs
|
|
|
|
|
with bidirectional data transfers and generic request/response
|
|
|
|
|
protocols (e.g. Task Management Functions and SMP in Serial
|
|
|
|
|
Attached SCSI).
|
2007-07-09 18:38:05 +08:00
|
|
|
|
2007-07-25 16:02:30 +08:00
|
|
|
endif # BLOCK
|
|
|
|
|
|
2005-11-04 15:43:35 +08:00
|
|
|
source block/Kconfig.iosched
|