Kconfig 2.6 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091
  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. Disable this option to remove the block layer support from the
  10. kernel. This may be useful for embedded devices.
  11. If this option is disabled:
  12. - block device files will become unusable
  13. - some filesystems (such as ext3) will become unavailable.
  14. Also, SCSI character devices and USB storage will be disabled since
  15. they make use of various block layer definitions and facilities.
  16. Say Y here unless you know you really don't want to mount disks and
  17. suchlike.
  18. if BLOCK
  19. config LBD
  20. bool "Support for large block devices and files"
  21. depends on !64BIT
  22. help
  23. Enable block devices or files of size 2TB and larger.
  24. This option is required to support the full capacity of large
  25. (2TB+) block devices, including RAID, disk, Network Block Device,
  26. Logical Volume Manager (LVM) and loopback.
  27. This option also enables support for single files larger than
  28. 2TB.
  29. If unsure, say N.
  30. config BLK_DEV_IO_TRACE
  31. bool "Support for tracing block io actions"
  32. depends on SYSFS
  33. select RELAY
  34. select DEBUG_FS
  35. select TRACEPOINTS
  36. help
  37. Say Y here if you want to be able to trace the block layer actions
  38. on a given queue. Tracing allows you to see any traffic happening
  39. on a block device queue. For more information (and the userspace
  40. support tools needed), fetch the blktrace tools from:
  41. git://git.kernel.dk/blktrace.git
  42. If unsure, say N.
  43. config BLK_DEV_BSG
  44. bool "Block layer SG support v4 (EXPERIMENTAL)"
  45. depends on EXPERIMENTAL
  46. ---help---
  47. Saying Y here will enable generic SG (SCSI generic) v4 support
  48. for any block device.
  49. Unlike SG v3 (aka block/scsi_ioctl.c drivers/scsi/sg.c), SG v4
  50. can handle complicated SCSI commands: tagged variable length cdbs
  51. with bidirectional data transfers and generic request/response
  52. protocols (e.g. Task Management Functions and SMP in Serial
  53. Attached SCSI).
  54. If unsure, say N.
  55. config BLK_DEV_INTEGRITY
  56. bool "Block layer data integrity support"
  57. ---help---
  58. Some storage devices allow extra information to be
  59. stored/retrieved to help protect the data. The block layer
  60. data integrity option provides hooks which can be used by
  61. filesystems to ensure better data integrity.
  62. Say yes here if you have a storage device that provides the
  63. T10/SCSI Data Integrity Field or the T13/ATA External Path
  64. Protection. If in doubt, say N.
  65. endif # BLOCK
  66. config BLOCK_COMPAT
  67. bool
  68. depends on BLOCK && COMPAT
  69. default y
  70. source block/Kconfig.iosched