Blame view
block/Kconfig
2.56 KB
3a65dfe8c
|
1 2 3 |
# # Block layer core configuration # |
16ed002f2
|
4 |
menuconfig BLOCK |
51d7513a8
|
5 |
bool "Enable the block layer" if EMBEDDED |
9361401eb
|
6 7 |
default y help |
ee86418d3
|
8 |
Provide block layer support for the kernel. |
9361401eb
|
9 |
|
ee86418d3
|
10 11 12 13 14 15 16 17 18 19 |
Disable this option to remove the block layer support from the kernel. This may be useful for embedded devices. If this option is disabled: - block device files will become unusable - some filesystems (such as ext3) will become unavailable. Also, SCSI character devices and USB storage will be disabled since they make use of various block layer definitions and facilities. |
9361401eb
|
20 21 22 23 24 |
Say Y here unless you know you really don't want to mount disks and suchlike. if BLOCK |
3a65dfe8c
|
25 |
config LBD |
b3a6ffe16
|
26 |
bool "Support for large block devices and files" |
e62438630
|
27 |
depends on !64BIT |
3a65dfe8c
|
28 |
help |
b3a6ffe16
|
29 |
Enable block devices or files of size 2TB and larger. |
ee86418d3
|
30 31 32 33 |
This option is required to support the full capacity of large (2TB+) block devices, including RAID, disk, Network Block Device, Logical Volume Manager (LVM) and loopback. |
b3a6ffe16
|
34 35 36 |
This option also enables support for single files larger than 2TB. |
ee86418d3
|
37 38 |
If unsure, say N. |
3a65dfe8c
|
39 |
|
2056a782f
|
40 41 |
config BLK_DEV_IO_TRACE bool "Support for tracing block io actions" |
09540e691
|
42 |
depends on SYSFS |
2056a782f
|
43 44 |
select RELAY select DEBUG_FS |
5f3ea37c7
|
45 |
select TRACEPOINTS |
2056a782f
|
46 |
help |
ee86418d3
|
47 |
Say Y here if you want to be able to trace the block layer actions |
2056a782f
|
48 |
on a given queue. Tracing allows you to see any traffic happening |
ee86418d3
|
49 50 |
on a block device queue. For more information (and the userspace support tools needed), fetch the blktrace tools from: |
2056a782f
|
51 |
|
75ce6facc
|
52 |
git://git.kernel.dk/blktrace.git |
2056a782f
|
53 |
|
ee86418d3
|
54 |
If unsure, say N. |
3d6392cfb
|
55 |
config BLK_DEV_BSG |
319a7b7fb
|
56 |
bool "Block layer SG support v4 (EXPERIMENTAL)" |
80ed71ce1
|
57 |
depends on EXPERIMENTAL |
3d6392cfb
|
58 |
---help--- |
ee86418d3
|
59 60 61 62 63 64 65 66 67 68 |
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). If unsure, say N. |
3d6392cfb
|
69 |
|
7ba1ba12e
|
70 71 72 73 74 75 76 77 78 79 80 |
config BLK_DEV_INTEGRITY bool "Block layer data integrity support" ---help--- Some storage devices allow extra information to be stored/retrieved to help protect the data. The block layer data integrity option provides hooks which can be used by filesystems to ensure better data integrity. Say yes here if you have a storage device that provides the T10/SCSI Data Integrity Field or the T13/ATA External Path Protection. If in doubt, say N. |
2b9e0aae1
|
81 |
endif # BLOCK |
99874d504
|
82 83 |
config BLOCK_COMPAT bool |
2b9e0aae1
|
84 |
depends on BLOCK && COMPAT |
99874d504
|
85 |
default y |
3a65dfe8c
|
86 |
source block/Kconfig.iosched |