block/Kconfig

   1 #
   2 # Block layer core configuration
   3 #
   4 menuconfig BLOCK
   5        bool "Enable the block layer" if EMBEDDED
   6        default y
   7        help
   8          Provide block layer support for the kernel.
   9
  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.
  20
  21          Say Y here unless you know you really don't want to mount disks and
  22          suchlike.
  23
  24 if BLOCK
  25
  26 config LBD
  27         bool "Support for large block devices and files"
  28         depends on !64BIT
  29         help
  30           Enable block devices or files of size 2TB and larger.
  31
  32           This option is required to support the full capacity of large
  33           (2TB+) block devices, including RAID, disk, Network Block Device,
  34           Logical Volume Manager (LVM) and loopback.
  35
  36           This option also enables support for single files larger than
  37           2TB.
  38
  39           The ext4 filesystem requires that this feature be enabled in
  40           order to support filesystems that have the huge_file feature
  41           enabled.    Otherwise, it will refuse to mount any filesystems
  42           that use the huge_file feature, which is enabled by default
  43           by mke2fs.ext4.   The GFS2 filesystem also requires this feature.
  44
  45           If unsure, say N.
  46
  47 config BLK_DEV_IO_TRACE
  48         bool "Support for tracing block io actions"
  49         depends on SYSFS
  50         select RELAY
  51         select DEBUG_FS
  52         select TRACEPOINTS
  53         help
  54           Say Y here if you want to be able to trace the block layer actions
  55           on a given queue. Tracing allows you to see any traffic happening
  56           on a block device queue. For more information (and the userspace
  57           support tools needed), fetch the blktrace tools from:
  58
  59           git://git.kernel.dk/blktrace.git
  60
  61           If unsure, say N.
  62
  63 config BLK_DEV_BSG
  64         bool "Block layer SG support v4 (EXPERIMENTAL)"
  65         depends on EXPERIMENTAL
  66         ---help---
  67           Saying Y here will enable generic SG (SCSI generic) v4 support
  68           for any block device.
  69
  70           Unlike SG v3 (aka block/scsi_ioctl.c drivers/scsi/sg.c), SG v4
  71           can handle complicated SCSI commands: tagged variable length cdbs
  72           with bidirectional data transfers and generic request/response
  73           protocols (e.g. Task Management Functions and SMP in Serial
  74           Attached SCSI).
  75
  76           If unsure, say N.
  77
  78 config BLK_DEV_INTEGRITY
  79         bool "Block layer data integrity support"
  80         ---help---
  81         Some storage devices allow extra information to be
  82         stored/retrieved to help protect the data.  The block layer
  83         data integrity option provides hooks which can be used by
  84         filesystems to ensure better data integrity.
  85
  86         Say yes here if you have a storage device that provides the
  87         T10/SCSI Data Integrity Field or the T13/ATA External Path
  88         Protection.  If in doubt, say N.
  89
  90 endif # BLOCK
  91
  92 config BLOCK_COMPAT
  93         bool
  94         depends on BLOCK && COMPAT
  95         default y
  96
  97 source block/Kconfig.iosched