drivers/block/Kconfig

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