drivers/block/Kconfig

   1 # SPDX-License-Identifier: GPL-2.0
   2 #
   3 # Block device driver configuration
   4 #
   5
   6 menuconfig BLK_DEV
   7         bool "Block devices"
   8         depends on BLOCK
   9         default y
  10         ---help---
  11           Say Y here to get to see options for various different block device
  12           drivers. This option alone does not add any kernel code.
  13
  14           If you say N, all options in this submenu will be skipped and disabled;
  15           only do this if you know what you are doing.
  16
  17 if BLK_DEV
  18
  19 config BLK_DEV_NULL_BLK
  20         tristate "Null test block driver"
  21         select CONFIGFS_FS
  22
  23 config BLK_DEV_FD
  24         tristate "Normal floppy disk support"
  25         depends on ARCH_MAY_HAVE_PC_FDC
  26         ---help---
  27           If you want to use the floppy disk drive(s) of your PC under Linux,
  28           say Y. Information about this driver, especially important for IBM
  29           Thinkpad users, is contained in
  30           <file:Documentation/blockdev/floppy.txt>.
  31           That file also contains the location of the Floppy driver FAQ as
  32           well as location of the fdutils package used to configure additional
  33           parameters of the driver at run time.
  34
  35           To compile this driver as a module, choose M here: the
  36           module will be called floppy.
  37
  38 config AMIGA_FLOPPY
  39         tristate "Amiga floppy support"
  40         depends on AMIGA
  41
  42 config ATARI_FLOPPY
  43         tristate "Atari floppy support"
  44         depends on ATARI
  45
  46 config MAC_FLOPPY
  47         tristate "Support for PowerMac floppy"
  48         depends on PPC_PMAC && !PPC_PMAC64
  49         help
  50           If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
  51           floppy controller, say Y here. Most commonly found in PowerMacs.
  52
  53 config BLK_DEV_SWIM
  54         tristate "Support for SWIM Macintosh floppy"
  55         depends on M68K && MAC
  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
  60 config AMIGA_Z2RAM
  61         tristate "Amiga Zorro II ramdisk support"
  62         depends on ZORRO
  63         help
  64           This enables support for using Chip RAM and Zorro II RAM as a
  65           ramdisk or as a swap partition. Say Y if you want to include this
  66           driver in the kernel.
  67
  68           To compile this driver as a module, choose M here: the
  69           module will be called z2ram.
  70
  71 config CDROM
  72         tristate
  73
  74 config GDROM
  75         tristate "SEGA Dreamcast GD-ROM drive"
  76         depends on SH_DREAMCAST
  77         select CDROM
  78         select BLK_SCSI_REQUEST # only for the generic cdrom code
  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
  87 config PARIDE
  88         tristate "Parallel port IDE device support"
  89         depends on PARPORT_PC
  90         ---help---
  91           There are many external CD-ROM and disk devices that connect through
  92           your computer's parallel port. Most of them are actually IDE devices
  93           using a parallel port IDE adapter. This option enables the PARIDE
  94           subsystem which contains drivers for many of these external drives.
  95           Read <file:Documentation/blockdev/paride.txt> for more information.
  96
  97           If you have said Y to the "Parallel-port support" configuration
  98           option, you may share a single port between your printer and other
  99           parallel port devices. Answer Y to build PARIDE support into your
 100           kernel, or M if you would like to build it as a loadable module. If
 101           your parallel port support is in a loadable module, you must build
 102           PARIDE as a module. If you built PARIDE support into your kernel,
 103           you may still build the individual protocol modules and high-level
 104           drivers as loadable modules. If you build this support as a module,
 105           it will be called paride.
 106
 107           To use the PARIDE support, you must say Y or M here and also to at
 108           least one high-level driver (e.g. "Parallel port IDE disks",
 109           "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
 110           to at least one protocol driver (e.g. "ATEN EH-100 protocol",
 111           "MicroSolutions backpack protocol", "DataStor Commuter protocol"
 112           etc.).
 113
 114 source "drivers/block/paride/Kconfig"
 115
 116 source "drivers/block/mtip32xx/Kconfig"
 117
 118 source "drivers/block/zram/Kconfig"
 119
 120 config BLK_DEV_DAC960
 121         tristate "Mylex DAC960/DAC1100 PCI RAID Controller support"
 122         depends on PCI
 123         help
 124           This driver adds support for the Mylex DAC960, AcceleRAID, and
 125           eXtremeRAID PCI RAID controllers.  See the file
 126           <file:Documentation/blockdev/README.DAC960> for further information
 127           about this driver.
 128
 129           To compile this driver as a module, choose M here: the
 130           module will be called DAC960.
 131
 132 config BLK_DEV_UMEM
 133         tristate "Micro Memory MM5415 Battery Backed RAM support"
 134         depends on PCI
 135         ---help---
 136           Saying Y here will include support for the MM5415 family of
 137           battery backed (Non-volatile) RAM cards.
 138           <http://www.umem.com/>
 139
 140           The cards appear as block devices that can be partitioned into
 141           as many as 15 partitions.
 142
 143           To compile this driver as a module, choose M here: the
 144           module will be called umem.
 145
 146           The umem driver has not yet been allocated a MAJOR number, so
 147           one is chosen dynamically.
 148
 149 config BLK_DEV_UBD
 150         bool "Virtual block device"
 151         depends on UML
 152         ---help---
 153           The User-Mode Linux port includes a driver called UBD which will let
 154           you access arbitrary files on the host computer as block devices.
 155           Unless you know that you do not need such virtual block devices say
 156           Y here.
 157
 158 config BLK_DEV_UBD_SYNC
 159         bool "Always do synchronous disk IO for UBD"
 160         depends on BLK_DEV_UBD
 161         ---help---
 162           Writes to the virtual block device are not immediately written to the
 163           host's disk; this may cause problems if, for example, the User-Mode
 164           Linux 'Virtual Machine' uses a journalling filesystem and the host
 165           computer crashes.
 166
 167           Synchronous operation (i.e. always writing data to the host's disk
 168           immediately) is configurable on a per-UBD basis by using a special
 169           kernel command line option.  Alternatively, you can say Y here to
 170           turn on synchronous operation by default for all block devices.
 171
 172           If you're running a journalling file system (like reiserfs, for
 173           example) in your virtual machine, you will want to say Y here.  If
 174           you care for the safety of the data in your virtual machine, Y is a
 175           wise choice too.  In all other cases (for example, if you're just
 176           playing around with User-Mode Linux) you can choose N.
 177
 178 config BLK_DEV_COW_COMMON
 179         bool
 180         default BLK_DEV_UBD
 181
 182 config BLK_DEV_LOOP
 183         tristate "Loopback device support"
 184         ---help---
 185           Saying Y here will allow you to use a regular file as a block
 186           device; you can then create a file system on that block device and
 187           mount it just as you would mount other block devices such as hard
 188           drive partitions, CD-ROM drives or floppy drives. The loop devices
 189           are block special device files with major number 7 and typically
 190           called /dev/loop0, /dev/loop1 etc.
 191
 192           This is useful if you want to check an ISO 9660 file system before
 193           burning the CD, or if you want to use floppy images without first
 194           writing them to floppy. Furthermore, some Linux distributions avoid
 195           the need for a dedicated Linux partition by keeping their complete
 196           root file system inside a DOS FAT file using this loop device
 197           driver.
 198
 199           To use the loop device, you need the losetup utility, found in the
 200           util-linux package, see
 201           <https://www.kernel.org/pub/linux/utils/util-linux/>.
 202
 203           The loop device driver can also be used to "hide" a file system in
 204           a disk partition, floppy, or regular file, either using encryption
 205           (scrambling the data) or steganography (hiding the data in the low
 206           bits of, say, a sound file). This is also safe if the file resides
 207           on a remote file server.
 208
 209           There are several ways of encrypting disks. Some of these require
 210           kernel patches. The vanilla kernel offers the cryptoloop option
 211           and a Device Mapper target (which is superior, as it supports all
 212           file systems). If you want to use the cryptoloop, say Y to both
 213           LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12
 214           or later) version of util-linux. Additionally, be aware that
 215           the cryptoloop is not safe for storing journaled filesystems.
 216
 217           Note that this loop device has nothing to do with the loopback
 218           device used for network connections from the machine to itself.
 219
 220           To compile this driver as a module, choose M here: the
 221           module will be called loop.
 222
 223           Most users will answer N here.
 224
 225 config BLK_DEV_LOOP_MIN_COUNT
 226         int "Number of loop devices to pre-create at init time"
 227         depends on BLK_DEV_LOOP
 228         default 8
 229         help
 230           Static number of loop devices to be unconditionally pre-created
 231           at init time.
 232
 233           This default value can be overwritten on the kernel command
 234           line or with module-parameter loop.max_loop.
 235
 236           The historic default is 8. If a late 2011 version of losetup(8)
 237           is used, it can be set to 0, since needed loop devices can be
 238           dynamically allocated with the /dev/loop-control interface.
 239
 240 config BLK_DEV_CRYPTOLOOP
 241         tristate "Cryptoloop Support"
 242         select CRYPTO
 243         select CRYPTO_CBC
 244         depends on BLK_DEV_LOOP
 245         ---help---
 246           Say Y here if you want to be able to use the ciphers that are
 247           provided by the CryptoAPI as loop transformation. This might be
 248           used as hard disk encryption.
 249
 250           WARNING: This device is not safe for journaled file systems like
 251           ext3 or Reiserfs. Please use the Device Mapper crypto module
 252           instead, which can be configured to be on-disk compatible with the
 253           cryptoloop device.
 254
 255 source "drivers/block/drbd/Kconfig"
 256
 257 config BLK_DEV_NBD
 258         tristate "Network block device support"
 259         depends on NET
 260         ---help---
 261           Saying Y here will allow your computer to be a client for network
 262           block devices, i.e. it will be able to use block devices exported by
 263           servers (mount file systems on them etc.). Communication between
 264           client and server works over TCP/IP networking, but to the client
 265           program this is hidden: it looks like a regular local file access to
 266           a block device special file such as /dev/nd0.
 267
 268           Network block devices also allows you to run a block-device in
 269           userland (making server and client physically the same computer,
 270           communicating using the loopback network device).
 271
 272           Read <file:Documentation/blockdev/nbd.txt> for more information,
 273           especially about where to find the server code, which runs in user
 274           space and does not need special kernel support.
 275
 276           Note that this has nothing to do with the network file systems NFS
 277           or Coda; you can say N here even if you intend to use NFS or Coda.
 278
 279           To compile this driver as a module, choose M here: the
 280           module will be called nbd.
 281
 282           If unsure, say N.
 283
 284 config BLK_DEV_SKD
 285         tristate "STEC S1120 Block Driver"
 286         depends on PCI
 287         depends on 64BIT
 288         ---help---
 289         Saying Y or M here will enable support for the
 290         STEC, Inc. S1120 PCIe SSD.
 291
 292         Use device /dev/skd$N amd /dev/skd$Np$M.
 293
 294 config BLK_DEV_SX8
 295         tristate "Promise SATA SX8 support"
 296         depends on PCI
 297         ---help---
 298           Saying Y or M here will enable support for the
 299           Promise SATA SX8 controllers.
 300
 301           Use devices /dev/sx8/$N and /dev/sx8/$Np$M.
 302
 303 config BLK_DEV_RAM
 304         tristate "RAM block device support"
 305         ---help---
 306           Saying Y here will allow you to use a portion of your RAM memory as
 307           a block device, so that you can make file systems on it, read and
 308           write to it and do all the other things that you can do with normal
 309           block devices (such as hard drives). It is usually used to load and
 310           store a copy of a minimal root file system off of a floppy into RAM
 311           during the initial install of Linux.
 312
 313           Note that the kernel command line option "ramdisk=XX" is now obsolete.
 314           For details, read <file:Documentation/blockdev/ramdisk.txt>.
 315
 316           To compile this driver as a module, choose M here: the
 317           module will be called brd. An alias "rd" has been defined
 318           for historical reasons.
 319
 320           Most normal users won't need the RAM disk functionality, and can
 321           thus say N here.
 322
 323 config BLK_DEV_RAM_COUNT
 324         int "Default number of RAM disks"
 325         default "16"
 326         depends on BLK_DEV_RAM
 327         help
 328           The default value is 16 RAM disks. Change this if you know what you
 329           are doing. If you boot from a filesystem that needs to be extracted
 330           in memory, you will need at least one RAM disk (e.g. root on cramfs).
 331
 332 config BLK_DEV_RAM_SIZE
 333         int "Default RAM disk size (kbytes)"
 334         depends on BLK_DEV_RAM
 335         default "4096"
 336         help
 337           The default value is 4096 kilobytes. Only change this if you know
 338           what you are doing.
 339
 340 config CDROM_PKTCDVD
 341         tristate "Packet writing on CD/DVD media (DEPRECATED)"
 342         depends on !UML
 343         select CDROM
 344         select BLK_SCSI_REQUEST
 345         help
 346           Note: This driver is deprecated and will be removed from the
 347           kernel in the near future!
 348
 349           If you have a CDROM/DVD drive that supports packet writing, say
 350           Y to include support. It should work with any MMC/Mt Fuji
 351           compliant ATAPI or SCSI drive, which is just about any newer
 352           DVD/CD writer.
 353
 354           Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs
 355           is possible.
 356           DVD-RW disks must be in restricted overwrite mode.
 357
 358           See the file <file:Documentation/cdrom/packet-writing.txt>
 359           for further information on the use of this driver.
 360
 361           To compile this driver as a module, choose M here: the
 362           module will be called pktcdvd.
 363
 364 config CDROM_PKTCDVD_BUFFERS
 365         int "Free buffers for data gathering"
 366         depends on CDROM_PKTCDVD
 367         default "8"
 368         help
 369           This controls the maximum number of active concurrent packets. More
 370           concurrent packets can increase write performance, but also require
 371           more memory. Each concurrent packet will require approximately 64Kb
 372           of non-swappable kernel memory, memory which will be allocated when
 373           a disc is opened for writing.
 374
 375 config CDROM_PKTCDVD_WCACHE
 376         bool "Enable write caching"
 377         depends on CDROM_PKTCDVD
 378         help
 379           If enabled, write caching will be set for the CD-R/W device. For now
 380           this option is dangerous unless the CD-RW media is known good, as we
 381           don't do deferred write error handling yet.
 382
 383 config ATA_OVER_ETH
 384         tristate "ATA over Ethernet support"
 385         depends on NET
 386         help
 387         This driver provides Support for ATA over Ethernet block
 388         devices like the Coraid EtherDrive (R) Storage Blade.
 389
 390 config SUNVDC
 391         tristate "Sun Virtual Disk Client support"
 392         depends on SUN_LDOMS
 393         help
 394           Support for virtual disk devices as a client under Sun
 395           Logical Domains.
 396
 397 source "drivers/s390/block/Kconfig"
 398
 399 config XILINX_SYSACE
 400         tristate "Xilinx SystemACE support"
 401         depends on 4xx || MICROBLAZE
 402         help
 403           Include support for the Xilinx SystemACE CompactFlash interface
 404
 405 config XEN_BLKDEV_FRONTEND
 406         tristate "Xen virtual block device support"
 407         depends on XEN
 408         default y
 409         select XEN_XENBUS_FRONTEND
 410         help
 411           This driver implements the front-end of the Xen virtual
 412           block device driver.  It communicates with a back-end driver
 413           in another domain which drives the actual block device.
 414
 415 config XEN_BLKDEV_BACKEND
 416         tristate "Xen block-device backend driver"
 417         depends on XEN_BACKEND
 418         help
 419           The block-device backend driver allows the kernel to export its
 420           block devices to other guests via a high-performance shared-memory
 421           interface.
 422
 423           The corresponding Linux frontend driver is enabled by the
 424           CONFIG_XEN_BLKDEV_FRONTEND configuration option.
 425
 426           The backend driver attaches itself to a any block device specified
 427           in the XenBus configuration. There are no limits to what the block
 428           device as long as it has a major and minor.
 429
 430           If you are compiling a kernel to run in a Xen block backend driver
 431           domain (often this is domain 0) you should say Y here. To
 432           compile this driver as a module, chose M here: the module
 433           will be called xen-blkback.
 434
 435
 436 config VIRTIO_BLK
 437         tristate "Virtio block driver"
 438         depends on VIRTIO
 439         ---help---
 440           This is the virtual block driver for virtio.  It can be used with
 441           QEMU based VMMs (like KVM or Xen).  Say Y or M.
 442
 443 config VIRTIO_BLK_SCSI
 444         bool "SCSI passthrough request for the Virtio block driver"
 445         depends on VIRTIO_BLK
 446         select BLK_SCSI_REQUEST
 447         ---help---
 448           Enable support for SCSI passthrough (e.g. the SG_IO ioctl) on
 449           virtio-blk devices.  This is only supported for the legacy
 450           virtio protocol and not enabled by default by any hypervisor.
 451           You probably want to use virtio-scsi instead.
 452
 453 config BLK_DEV_RBD
 454         tristate "Rados block device (RBD)"
 455         depends on INET && BLOCK
 456         select CEPH_LIB
 457         select LIBCRC32C
 458         select CRYPTO_AES
 459         select CRYPTO
 460         default n
 461         help
 462           Say Y here if you want include the Rados block device, which stripes
 463           a block device over objects stored in the Ceph distributed object
 464           store.
 465
 466           More information at http://ceph.newdream.net/.
 467
 468           If unsure, say N.
 469
 470 config BLK_DEV_RSXX
 471         tristate "IBM Flash Adapter 900GB Full Height PCIe Device Driver"
 472         depends on PCI
 473         help
 474           Device driver for IBM's high speed PCIe SSD
 475           storage device: Flash Adapter 900GB Full Height.
 476
 477           To compile this driver as a module, choose M here: the
 478           module will be called rsxx.
 479
 480 endif # BLK_DEV