2 # Block layer core configuration
5 bool "Enable the block layer" if EMBEDDED
8 This permits the block layer to be removed from the kernel if it's not
9 needed (on some embedded devices for example). If this option is
10 disabled, then blockdev files will become unusable and some
11 filesystems (such as ext3) will become unavailable.
13 This option will also disable SCSI character devices and USB storage
14 since they make use of various block layer definitions and
17 Say Y here unless you know you really don't want to mount disks and
23 bool "Support for Large Block Devices"
26 Say Y here if you want to attach large (bigger than 2TB) discs to
27 your machine, or if you want to have a raid or loopback device
28 bigger than 2TB. Otherwise say N.
30 config BLK_DEV_IO_TRACE
31 bool "Support for tracing block io actions"
36 Say Y here, if you want to be able to trace the block layer actions
37 on a given queue. Tracing allows you to see any traffic happening
38 on a block device queue. For more information (and the user space
39 support tools needed), fetch the blktrace app from:
41 git://brick.kernel.dk/data/git/blktrace.git
44 bool "Support for Large Single Files"
47 Say Y here if you want to be able to handle very large files (bigger
48 than 2TB), otherwise say N.
53 bool "Block layer SG support v4 (EXPERIMENTAL)"
54 depends on EXPERIMENTAL
56 Saying Y here will enable generic SG (SCSI generic) v4 support
59 Unlike SG v3 (aka block/scsi_ioctl.c drivers/scsi/sg.c), SG v4
60 can handle complicated SCSI commands: tagged variable length cdbs
61 with bidirectional data transfers and generic request/response
62 protocols (e.g. Task Management Functions and SMP in Serial
69 depends on BLOCK && COMPAT
72 source block/Kconfig.iosched