2 # Block layer core configuration
5 bool "Enable the block layer" if EMBEDDED
8 Provide block layer support for the kernel.
10 Disable this option to remove the block layer support from the
11 kernel. This may be useful for embedded devices.
13 If this option is disabled:
15 - block device files will become unusable
16 - some filesystems (such as ext3) will become unavailable.
18 Also, SCSI character devices and USB storage will be disabled since
19 they make use of various block layer definitions and facilities.
21 Say Y here unless you know you really don't want to mount disks and
27 bool "Support for large (2TB+) block devices and files"
31 Enable block devices or files of size 2TB and larger.
33 This option is required to support the full capacity of large
34 (2TB+) block devices, including RAID, disk, Network Block Device,
35 Logical Volume Manager (LVM) and loopback.
37 This option also enables support for single files larger than
40 The ext4 filesystem requires that this feature be enabled in
41 order to support filesystems that have the huge_file feature
42 enabled. Otherwise, it will refuse to mount in the read-write
43 mode any filesystems that use the huge_file feature, which is
44 enabled by default by mke2fs.ext4.
46 The GFS2 filesystem also requires this feature.
51 bool "Block layer SG support v4"
54 Saying Y here will enable generic SG (SCSI generic) v4 support
57 Unlike SG v3 (aka block/scsi_ioctl.c drivers/scsi/sg.c), SG v4
58 can handle complicated SCSI commands: tagged variable length cdbs
59 with bidirectional data transfers and generic request/response
60 protocols (e.g. Task Management Functions and SMP in Serial
63 This option is required by recent UDEV versions to properly
64 access device serial numbers, etc.
68 config BLK_DEV_INTEGRITY
69 bool "Block layer data integrity support"
71 Some storage devices allow extra information to be
72 stored/retrieved to help protect the data. The block layer
73 data integrity option provides hooks which can be used by
74 filesystems to ensure better data integrity.
76 Say yes here if you have a storage device that provides the
77 T10/SCSI Data Integrity Field or the T13/ATA External Path
78 Protection. If in doubt, say N.
81 tristate "Block cgroup support"
83 depends on CFQ_GROUP_IOSCHED
86 Generic block IO controller cgroup interface. This is the common
87 cgroup interface which should be used by various IO controlling
90 Currently, CFQ IO scheduler uses it to recognize task groups and
91 control disk bandwidth allocation (proportional time slice allocation)
94 config DEBUG_BLK_CGROUP
99 Enable some debugging help. Currently it stores the cgroup path
100 in the blk group which can be used by cfq for tracing various
101 group related activity.
107 depends on BLOCK && COMPAT
110 source block/Kconfig.iosched