git://bbs.cooldavid.org / net-next-2.6.git / blame
| Commit | Line | Data |
|---|---|---|
| 3a65dfe8 JA |
1 | # |
| 2 | # Block layer core configuration | |
| 3 | # | |
| 16ed002f | 4 | menuconfig BLOCK |
| 51d7513a | 5 | bool "Enable the block layer" if EMBEDDED |
| 9361401e DH |
6 | default y |
| 7 | help | |
| ee86418d | 8 | Provide block layer support for the kernel. |
| 9361401e | 9 | |
| ee86418d NA |
10 | Disable this option to remove the block layer support from the |
| 11 | kernel. This may be useful for embedded devices. | |
| 12 | ||
| 13 | If this option is disabled: | |
| 14 | ||
| 15 | - block device files will become unusable | |
| 16 | - some filesystems (such as ext3) will become unavailable. | |
| 17 | ||
| 18 | Also, SCSI character devices and USB storage will be disabled since | |
| 19 | they make use of various block layer definitions and facilities. | |
| 9361401e DH |
20 | |
| 21 | Say Y here unless you know you really don't want to mount disks and | |
| 22 | suchlike. | |
| 23 | ||
| 24 | if BLOCK | |
| 25 | ||
| 3a65dfe8 | 26 | config LBD |
| b3a6ffe1 | 27 | bool "Support for large block devices and files" |
| e6243863 | 28 | depends on !64BIT |
| db29a6b4 | 29 | default y |
| 3a65dfe8 | 30 | help |
| b3a6ffe1 | 31 | Enable block devices or files of size 2TB and larger. |
| ee86418d NA |
32 | |
| 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. | |
| b3a6ffe1 JA |
36 | |
| 37 | This option also enables support for single files larger than | |
| 38 | 2TB. | |
| ee86418d | 39 | |
| 4d783b09 TT |
40 | The ext4 filesystem requires that this feature be enabled in |
| 41 | order to support filesystems that have the huge_file feature | |
| db29a6b4 BZ |
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. | |
| 4d783b09 | 45 | |
| db29a6b4 BZ |
46 | The GFS2 filesystem also requires this feature. |
| 47 | ||
| 48 | If unsure, say Y. | |
| 3a65dfe8 | 49 | |
| 3d6392cf | 50 | config BLK_DEV_BSG |
| 319a7b7f | 51 | bool "Block layer SG support v4 (EXPERIMENTAL)" |
| 80ed71ce | 52 | depends on EXPERIMENTAL |
| 3d6392cf | 53 | ---help--- |
| ee86418d NA |
54 | Saying Y here will enable generic SG (SCSI generic) v4 support |
| 55 | for any block device. | |
| 56 | ||
| 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 | |
| 61 | Attached SCSI). | |
| 62 | ||
| 63 | If unsure, say N. | |
| 3d6392cf | 64 | |
| 7ba1ba12 MP |
65 | config BLK_DEV_INTEGRITY |
| 66 | bool "Block layer data integrity support" | |
| 67 | ---help--- | |
| 68 | Some storage devices allow extra information to be | |
| 69 | stored/retrieved to help protect the data. The block layer | |
| 70 | data integrity option provides hooks which can be used by | |
| 71 | filesystems to ensure better data integrity. | |
| 72 | ||
| 73 | Say yes here if you have a storage device that provides the | |
| 74 | T10/SCSI Data Integrity Field or the T13/ATA External Path | |
| 75 | Protection. If in doubt, say N. | |
| 76 | ||
| 2b9e0aae LT |
77 | endif # BLOCK |
| 78 | ||
| 99874d50 JA |
79 | config BLOCK_COMPAT |
| 80 | bool | |
| 2b9e0aae | 81 | depends on BLOCK && COMPAT |
| 99874d50 JA |
82 | default y |
| 83 | ||
| 3a65dfe8 | 84 | source block/Kconfig.iosched |