Kconfig 15 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428
  1. # SPDX-License-Identifier: GPL-2.0
  2. #
  3. # Block device driver configuration
  4. #
  5. menuconfig BLK_DEV
  6. bool "Block devices"
  7. depends on BLOCK
  8. default y
  9. help
  10. Say Y here to get to see options for various different block device
  11. drivers. This option alone does not add any kernel code.
  12. If you say N, all options in this submenu will be skipped and disabled;
  13. only do this if you know what you are doing.
  14. if BLK_DEV
  15. source "drivers/block/null_blk/Kconfig"
  16. config BLK_DEV_FD
  17. tristate "Normal floppy disk support"
  18. depends on ARCH_MAY_HAVE_PC_FDC
  19. help
  20. If you want to use the floppy disk drive(s) of your PC under Linux,
  21. say Y. Information about this driver, especially important for IBM
  22. Thinkpad users, is contained in
  23. <file:Documentation/admin-guide/blockdev/floppy.rst>.
  24. That file also contains the location of the Floppy driver FAQ as
  25. well as location of the fdutils package used to configure additional
  26. parameters of the driver at run time.
  27. To compile this driver as a module, choose M here: the
  28. module will be called floppy.
  29. config BLK_DEV_FD_RAWCMD
  30. bool "Support for raw floppy disk commands (DEPRECATED)"
  31. depends on BLK_DEV_FD
  32. help
  33. If you want to use actual physical floppies and expect to do
  34. special low-level hardware accesses to them (access and use
  35. non-standard formats, for example), then enable this.
  36. Note that the code enabled by this option is rarely used and
  37. might be unstable or insecure, and distros should not enable it.
  38. Note: FDRAWCMD is deprecated and will be removed from the kernel
  39. in the near future.
  40. If unsure, say N.
  41. config AMIGA_FLOPPY
  42. tristate "Amiga floppy support"
  43. depends on AMIGA
  44. config ATARI_FLOPPY
  45. tristate "Atari floppy support"
  46. depends on ATARI
  47. config MAC_FLOPPY
  48. tristate "Support for PowerMac floppy"
  49. depends on PPC_PMAC && !PPC_PMAC64
  50. help
  51. If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
  52. floppy controller, say Y here. Most commonly found in PowerMacs.
  53. config BLK_DEV_SWIM
  54. tristate "Support for SWIM Macintosh floppy"
  55. depends on M68K && MAC && !HIGHMEM
  56. help
  57. You should select this option if you want floppy support
  58. and you don't have a II, IIfx, Q900, Q950 or AV series.
  59. config AMIGA_Z2RAM
  60. tristate "Amiga Zorro II ramdisk support"
  61. depends on ZORRO
  62. help
  63. This enables support for using Chip RAM and Zorro II RAM as a
  64. ramdisk or as a swap partition. Say Y if you want to include this
  65. driver in the kernel.
  66. To compile this driver as a module, choose M here: the
  67. module will be called z2ram.
  68. config N64CART
  69. bool "N64 cart support"
  70. depends on MACH_NINTENDO64
  71. help
  72. Support for the N64 cart.
  73. config CDROM
  74. tristate
  75. config GDROM
  76. tristate "SEGA Dreamcast GD-ROM drive"
  77. depends on SH_DREAMCAST
  78. select CDROM
  79. help
  80. A standard SEGA Dreamcast comes with a modified CD ROM drive called a
  81. "GD-ROM" by SEGA to signify it is capable of reading special disks
  82. with up to 1 GB of data. This drive will also read standard CD ROM
  83. disks. Select this option to access any disks in your GD ROM drive.
  84. Most users will want to say "Y" here.
  85. You can also build this as a module which will be called gdrom.
  86. config PARIDE
  87. tristate "Parallel port IDE device support"
  88. depends on PARPORT_PC
  89. help
  90. There are many external CD-ROM and disk devices that connect through
  91. your computer's parallel port. Most of them are actually IDE devices
  92. using a parallel port IDE adapter. This option enables the PARIDE
  93. subsystem which contains drivers for many of these external drives.
  94. Read <file:Documentation/admin-guide/blockdev/paride.rst> for more information.
  95. If you have said Y to the "Parallel-port support" configuration
  96. option, you may share a single port between your printer and other
  97. parallel port devices. Answer Y to build PARIDE support into your
  98. kernel, or M if you would like to build it as a loadable module. If
  99. your parallel port support is in a loadable module, you must build
  100. PARIDE as a module. If you built PARIDE support into your kernel,
  101. you may still build the individual protocol modules and high-level
  102. drivers as loadable modules. If you build this support as a module,
  103. it will be called paride.
  104. To use the PARIDE support, you must say Y or M here and also to at
  105. least one high-level driver (e.g. "Parallel port IDE disks",
  106. "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
  107. to at least one protocol driver (e.g. "ATEN EH-100 protocol",
  108. "MicroSolutions backpack protocol", "DataStor Commuter protocol"
  109. etc.).
  110. source "drivers/block/paride/Kconfig"
  111. source "drivers/block/mtip32xx/Kconfig"
  112. source "drivers/block/zram/Kconfig"
  113. config BLK_DEV_UBD
  114. bool "Virtual block device"
  115. depends on UML
  116. help
  117. The User-Mode Linux port includes a driver called UBD which will let
  118. you access arbitrary files on the host computer as block devices.
  119. Unless you know that you do not need such virtual block devices say
  120. Y here.
  121. config BLK_DEV_UBD_SYNC
  122. bool "Always do synchronous disk IO for UBD"
  123. depends on BLK_DEV_UBD
  124. help
  125. Writes to the virtual block device are not immediately written to the
  126. host's disk; this may cause problems if, for example, the User-Mode
  127. Linux 'Virtual Machine' uses a journalling filesystem and the host
  128. computer crashes.
  129. Synchronous operation (i.e. always writing data to the host's disk
  130. immediately) is configurable on a per-UBD basis by using a special
  131. kernel command line option. Alternatively, you can say Y here to
  132. turn on synchronous operation by default for all block devices.
  133. If you're running a journalling file system (like reiserfs, for
  134. example) in your virtual machine, you will want to say Y here. If
  135. you care for the safety of the data in your virtual machine, Y is a
  136. wise choice too. In all other cases (for example, if you're just
  137. playing around with User-Mode Linux) you can choose N.
  138. config BLK_DEV_COW_COMMON
  139. bool
  140. default BLK_DEV_UBD
  141. config BLK_DEV_LOOP
  142. tristate "Loopback device support"
  143. help
  144. Saying Y here will allow you to use a regular file as a block
  145. device; you can then create a file system on that block device and
  146. mount it just as you would mount other block devices such as hard
  147. drive partitions, CD-ROM drives or floppy drives. The loop devices
  148. are block special device files with major number 7 and typically
  149. called /dev/loop0, /dev/loop1 etc.
  150. This is useful if you want to check an ISO 9660 file system before
  151. burning the CD, or if you want to use floppy images without first
  152. writing them to floppy. Furthermore, some Linux distributions avoid
  153. the need for a dedicated Linux partition by keeping their complete
  154. root file system inside a DOS FAT file using this loop device
  155. driver.
  156. To use the loop device, you need the losetup utility, found in the
  157. util-linux package, see
  158. <https://www.kernel.org/pub/linux/utils/util-linux/>.
  159. The loop device driver can also be used to "hide" a file system in
  160. a disk partition, floppy, or regular file, either using encryption
  161. (scrambling the data) or steganography (hiding the data in the low
  162. bits of, say, a sound file). This is also safe if the file resides
  163. on a remote file server.
  164. Note that this loop device has nothing to do with the loopback
  165. device used for network connections from the machine to itself.
  166. To compile this driver as a module, choose M here: the
  167. module will be called loop.
  168. Most users will answer N here.
  169. config BLK_DEV_LOOP_MIN_COUNT
  170. int "Number of loop devices to pre-create at init time"
  171. depends on BLK_DEV_LOOP
  172. default 8
  173. help
  174. Static number of loop devices to be unconditionally pre-created
  175. at init time.
  176. This default value can be overwritten on the kernel command
  177. line or with module-parameter loop.max_loop.
  178. The historic default is 8. If a late 2011 version of losetup(8)
  179. is used, it can be set to 0, since needed loop devices can be
  180. dynamically allocated with the /dev/loop-control interface.
  181. source "drivers/block/drbd/Kconfig"
  182. config BLK_DEV_NBD
  183. tristate "Network block device support"
  184. depends on NET
  185. help
  186. Saying Y here will allow your computer to be a client for network
  187. block devices, i.e. it will be able to use block devices exported by
  188. servers (mount file systems on them etc.). Communication between
  189. client and server works over TCP/IP networking, but to the client
  190. program this is hidden: it looks like a regular local file access to
  191. a block device special file such as /dev/nd0.
  192. Network block devices also allows you to run a block-device in
  193. userland (making server and client physically the same computer,
  194. communicating using the loopback network device).
  195. Read <file:Documentation/admin-guide/blockdev/nbd.rst> for more information,
  196. especially about where to find the server code, which runs in user
  197. space and does not need special kernel support.
  198. Note that this has nothing to do with the network file systems NFS
  199. or Coda; you can say N here even if you intend to use NFS or Coda.
  200. To compile this driver as a module, choose M here: the
  201. module will be called nbd.
  202. If unsure, say N.
  203. config BLK_DEV_RAM
  204. tristate "RAM block device support"
  205. help
  206. Saying Y here will allow you to use a portion of your RAM memory as
  207. a block device, so that you can make file systems on it, read and
  208. write to it and do all the other things that you can do with normal
  209. block devices (such as hard drives). It is usually used to load and
  210. store a copy of a minimal root file system off of a floppy into RAM
  211. during the initial install of Linux.
  212. Note that the kernel command line option "ramdisk=XX" is now obsolete.
  213. For details, read <file:Documentation/admin-guide/blockdev/ramdisk.rst>.
  214. To compile this driver as a module, choose M here: the
  215. module will be called brd. An alias "rd" has been defined
  216. for historical reasons.
  217. Most normal users won't need the RAM disk functionality, and can
  218. thus say N here.
  219. config BLK_DEV_RAM_COUNT
  220. int "Default number of RAM disks"
  221. default "16"
  222. depends on BLK_DEV_RAM
  223. help
  224. The default value is 16 RAM disks. Change this if you know what you
  225. are doing. If you boot from a filesystem that needs to be extracted
  226. in memory, you will need at least one RAM disk (e.g. root on cramfs).
  227. config BLK_DEV_RAM_SIZE
  228. int "Default RAM disk size (kbytes)"
  229. depends on BLK_DEV_RAM
  230. default "4096"
  231. help
  232. The default value is 4096 kilobytes. Only change this if you know
  233. what you are doing.
  234. config CDROM_PKTCDVD
  235. tristate "Packet writing on CD/DVD media (DEPRECATED)"
  236. depends on !UML
  237. depends on SCSI
  238. select CDROM
  239. help
  240. Note: This driver is deprecated and will be removed from the
  241. kernel in the near future!
  242. If you have a CDROM/DVD drive that supports packet writing, say
  243. Y to include support. It should work with any MMC/Mt Fuji
  244. compliant ATAPI or SCSI drive, which is just about any newer
  245. DVD/CD writer.
  246. Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs
  247. is possible.
  248. DVD-RW disks must be in restricted overwrite mode.
  249. See the file <file:Documentation/cdrom/packet-writing.rst>
  250. for further information on the use of this driver.
  251. To compile this driver as a module, choose M here: the
  252. module will be called pktcdvd.
  253. config CDROM_PKTCDVD_BUFFERS
  254. int "Free buffers for data gathering"
  255. depends on CDROM_PKTCDVD
  256. default "8"
  257. help
  258. This controls the maximum number of active concurrent packets. More
  259. concurrent packets can increase write performance, but also require
  260. more memory. Each concurrent packet will require approximately 64Kb
  261. of non-swappable kernel memory, memory which will be allocated when
  262. a disc is opened for writing.
  263. config CDROM_PKTCDVD_WCACHE
  264. bool "Enable write caching"
  265. depends on CDROM_PKTCDVD
  266. help
  267. If enabled, write caching will be set for the CD-R/W device. For now
  268. this option is dangerous unless the CD-RW media is known good, as we
  269. don't do deferred write error handling yet.
  270. config ATA_OVER_ETH
  271. tristate "ATA over Ethernet support"
  272. depends on NET
  273. help
  274. This driver provides Support for ATA over Ethernet block
  275. devices like the Coraid EtherDrive (R) Storage Blade.
  276. config SUNVDC
  277. tristate "Sun Virtual Disk Client support"
  278. depends on SUN_LDOMS
  279. help
  280. Support for virtual disk devices as a client under Sun
  281. Logical Domains.
  282. source "drivers/s390/block/Kconfig"
  283. config XEN_BLKDEV_FRONTEND
  284. tristate "Xen virtual block device support"
  285. depends on XEN
  286. default y
  287. select XEN_XENBUS_FRONTEND
  288. help
  289. This driver implements the front-end of the Xen virtual
  290. block device driver. It communicates with a back-end driver
  291. in another domain which drives the actual block device.
  292. config XEN_BLKDEV_BACKEND
  293. tristate "Xen block-device backend driver"
  294. depends on XEN_BACKEND
  295. help
  296. The block-device backend driver allows the kernel to export its
  297. block devices to other guests via a high-performance shared-memory
  298. interface.
  299. The corresponding Linux frontend driver is enabled by the
  300. CONFIG_XEN_BLKDEV_FRONTEND configuration option.
  301. The backend driver attaches itself to a any block device specified
  302. in the XenBus configuration. There are no limits to what the block
  303. device as long as it has a major and minor.
  304. If you are compiling a kernel to run in a Xen block backend driver
  305. domain (often this is domain 0) you should say Y here. To
  306. compile this driver as a module, chose M here: the module
  307. will be called xen-blkback.
  308. config VIRTIO_BLK
  309. tristate "Virtio block driver"
  310. depends on VIRTIO
  311. select SG_POOL
  312. help
  313. This is the virtual block driver for virtio. It can be used with
  314. QEMU based VMMs (like KVM or Xen). Say Y or M.
  315. config VIRTIO_BLK_QTI_CRYPTO
  316. tristate "Vendor specific VIRTIO Crypto Engine Support"
  317. depends on VIRTIO_BLK && QTI_CRYPTO_VIRTUALIZATION
  318. help
  319. Enable storage inline crypto engine support for guest virtual machine.
  320. Enabling this allows kernel to use crypto operations defined
  321. and implemented by QTI.
  322. Say Y or M.
  323. config BLK_DEV_RBD
  324. tristate "Rados block device (RBD)"
  325. depends on INET && BLOCK
  326. select CEPH_LIB
  327. select LIBCRC32C
  328. select CRYPTO_AES
  329. select CRYPTO
  330. help
  331. Say Y here if you want include the Rados block device, which stripes
  332. a block device over objects stored in the Ceph distributed object
  333. store.
  334. More information at http://ceph.newdream.net/.
  335. If unsure, say N.
  336. config BLK_DEV_UBLK
  337. tristate "Userspace block driver (Experimental)"
  338. select IO_URING
  339. help
  340. io_uring based userspace block driver. Together with ublk server, ublk
  341. has been working well, but interface with userspace or command data
  342. definition isn't finalized yet, and might change according to future
  343. requirement, so mark is as experimental now.
  344. Say Y if you want to get better performance because task_work_add()
  345. can be used in IO path for replacing io_uring cmd, which will become
  346. shared between IO tasks and ubq daemon, meantime task_work_add() can
  347. can handle batch more effectively, but task_work_add() isn't exported
  348. for module, so ublk has to be built to kernel.
  349. source "drivers/block/rnbd/Kconfig"
  350. endif # BLK_DEV