[linux-2.6-block.git] / drivers / block / Kconfig

# SPDX-License-Identifier: GPL-2.0
#
# Block device driver configuration
#

menuconfig BLK_DEV
	bool "Block devices"
	depends on BLOCK
	default y
	---help---
	  Say Y here to get to see options for various different block device
	  drivers. This option alone does not add any kernel code.

	  If you say N, all options in this submenu will be skipped and disabled;
	  only do this if you know what you are doing.

if BLK_DEV

config BLK_DEV_NULL_BLK
	tristate "Null test block driver"
	select CONFIGFS_FS

config BLK_DEV_NULL_BLK_FAULT_INJECTION
	bool "Support fault injection for Null test block driver"
	depends on BLK_DEV_NULL_BLK && FAULT_INJECTION

config BLK_DEV_FD
	tristate "Normal floppy disk support"
	depends on ARCH_MAY_HAVE_PC_FDC
	---help---
	  If you want to use the floppy disk drive(s) of your PC under Linux,
	  say Y. Information about this driver, especially important for IBM
	  Thinkpad users, is contained in
	  <file:Documentation/blockdev/floppy.txt>.
	  That file also contains the location of the Floppy driver FAQ as
	  well as location of the fdutils package used to configure additional
	  parameters of the driver at run time.

	  To compile this driver as a module, choose M here: the
	  module will be called floppy.

config AMIGA_FLOPPY
	tristate "Amiga floppy support"
	depends on AMIGA

config ATARI_FLOPPY
	tristate "Atari floppy support"
	depends on ATARI

config MAC_FLOPPY
	tristate "Support for PowerMac floppy"
	depends on PPC_PMAC && !PPC_PMAC64
	help
	  If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
	  floppy controller, say Y here. Most commonly found in PowerMacs.

config BLK_DEV_SWIM
	tristate "Support for SWIM Macintosh floppy"
	depends on M68K && MAC
	help
	  You should select this option if you want floppy support
	  and you don't have a II, IIfx, Q900, Q950 or AV series.

config AMIGA_Z2RAM
	tristate "Amiga Zorro II ramdisk support"
	depends on ZORRO
	help
	  This enables support for using Chip RAM and Zorro II RAM as a
	  ramdisk or as a swap partition. Say Y if you want to include this
	  driver in the kernel.

	  To compile this driver as a module, choose M here: the
	  module will be called z2ram.

config CDROM
	tristate
	select BLK_SCSI_REQUEST

config GDROM
	tristate "SEGA Dreamcast GD-ROM drive"
	depends on SH_DREAMCAST
	select CDROM
	help
	  A standard SEGA Dreamcast comes with a modified CD ROM drive called a
	  "GD-ROM" by SEGA to signify it is capable of reading special disks
	  with up to 1 GB of data. This drive will also read standard CD ROM
	  disks. Select this option to access any disks in your GD ROM drive.
	  Most users will want to say "Y" here.
	  You can also build this as a module which will be called gdrom.

config PARIDE
	tristate "Parallel port IDE device support"
	depends on PARPORT_PC
	---help---
	  There are many external CD-ROM and disk devices that connect through
	  your computer's parallel port. Most of them are actually IDE devices
	  using a parallel port IDE adapter. This option enables the PARIDE
	  subsystem which contains drivers for many of these external drives.
	  Read <file:Documentation/blockdev/paride.txt> for more information.

	  If you have said Y to the "Parallel-port support" configuration
	  option, you may share a single port between your printer and other
	  parallel port devices. Answer Y to build PARIDE support into your
	  kernel, or M if you would like to build it as a loadable module. If
	  your parallel port support is in a loadable module, you must build
	  PARIDE as a module. If you built PARIDE support into your kernel,
	  you may still build the individual protocol modules and high-level
	  drivers as loadable modules. If you build this support as a module,
	  it will be called paride.

	  To use the PARIDE support, you must say Y or M here and also to at
	  least one high-level driver (e.g. "Parallel port IDE disks",
	  "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
	  to at least one protocol driver (e.g. "ATEN EH-100 protocol",
	  "MicroSolutions backpack protocol", "DataStor Commuter protocol"
	  etc.).

source "drivers/block/paride/Kconfig"

source "drivers/block/mtip32xx/Kconfig"

source "drivers/block/zram/Kconfig"

config BLK_DEV_UMEM
	tristate "Micro Memory MM5415 Battery Backed RAM support"
	depends on PCI
	---help---
	  Saying Y here will include support for the MM5415 family of
	  battery backed (Non-volatile) RAM cards.
	  <http://www.umem.com/>

	  The cards appear as block devices that can be partitioned into
	  as many as 15 partitions.

	  To compile this driver as a module, choose M here: the
	  module will be called umem.

	  The umem driver has not yet been allocated a MAJOR number, so
	  one is chosen dynamically.

config BLK_DEV_UBD
	bool "Virtual block device"
	depends on UML
	---help---
          The User-Mode Linux port includes a driver called UBD which will let
          you access arbitrary files on the host computer as block devices.
          Unless you know that you do not need such virtual block devices say
          Y here.

config BLK_DEV_UBD_SYNC
	bool "Always do synchronous disk IO for UBD"
	depends on BLK_DEV_UBD
	---help---
	  Writes to the virtual block device are not immediately written to the
	  host's disk; this may cause problems if, for example, the User-Mode
	  Linux 'Virtual Machine' uses a journalling filesystem and the host
	  computer crashes.

          Synchronous operation (i.e. always writing data to the host's disk
          immediately) is configurable on a per-UBD basis by using a special
          kernel command line option.  Alternatively, you can say Y here to
          turn on synchronous operation by default for all block devices.

          If you're running a journalling file system (like reiserfs, for
          example) in your virtual machine, you will want to say Y here.  If
          you care for the safety of the data in your virtual machine, Y is a
          wise choice too.  In all other cases (for example, if you're just
          playing around with User-Mode Linux) you can choose N.

config BLK_DEV_COW_COMMON
	bool
	default BLK_DEV_UBD

config BLK_DEV_LOOP
	tristate "Loopback device support"
	---help---
	  Saying Y here will allow you to use a regular file as a block
	  device; you can then create a file system on that block device and
	  mount it just as you would mount other block devices such as hard
	  drive partitions, CD-ROM drives or floppy drives. The loop devices
	  are block special device files with major number 7 and typically
	  called /dev/loop0, /dev/loop1 etc.

	  This is useful if you want to check an ISO 9660 file system before
	  burning the CD, or if you want to use floppy images without first
	  writing them to floppy. Furthermore, some Linux distributions avoid
	  the need for a dedicated Linux partition by keeping their complete
	  root file system inside a DOS FAT file using this loop device
	  driver.

	  To use the loop device, you need the losetup utility, found in the
	  util-linux package, see
	  <https://www.kernel.org/pub/linux/utils/util-linux/>.

	  The loop device driver can also be used to "hide" a file system in
	  a disk partition, floppy, or regular file, either using encryption
	  (scrambling the data) or steganography (hiding the data in the low
	  bits of, say, a sound file). This is also safe if the file resides
	  on a remote file server.

	  There are several ways of encrypting disks. Some of these require
	  kernel patches. The vanilla kernel offers the cryptoloop option
	  and a Device Mapper target (which is superior, as it supports all
	  file systems). If you want to use the cryptoloop, say Y to both
	  LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12
	  or later) version of util-linux. Additionally, be aware that
	  the cryptoloop is not safe for storing journaled filesystems.

	  Note that this loop device has nothing to do with the loopback
	  device used for network connections from the machine to itself.

	  To compile this driver as a module, choose M here: the
	  module will be called loop.

	  Most users will answer N here.

config BLK_DEV_LOOP_MIN_COUNT
	int "Number of loop devices to pre-create at init time"
	depends on BLK_DEV_LOOP
	default 8
	help
	  Static number of loop devices to be unconditionally pre-created
	  at init time.

	  This default value can be overwritten on the kernel command
	  line or with module-parameter loop.max_loop.

	  The historic default is 8. If a late 2011 version of losetup(8)
	  is used, it can be set to 0, since needed loop devices can be
	  dynamically allocated with the /dev/loop-control interface.

config BLK_DEV_CRYPTOLOOP
	tristate "Cryptoloop Support"
	select CRYPTO
	select CRYPTO_CBC
	depends on BLK_DEV_LOOP
	---help---
	  Say Y here if you want to be able to use the ciphers that are 
	  provided by the CryptoAPI as loop transformation. This might be
	  used as hard disk encryption.

	  WARNING: This device is not safe for journaled file systems like
	  ext3 or Reiserfs. Please use the Device Mapper crypto module
	  instead, which can be configured to be on-disk compatible with the
	  cryptoloop device.

source "drivers/block/drbd/Kconfig"

config BLK_DEV_NBD
	tristate "Network block device support"
	depends on NET
	---help---
	  Saying Y here will allow your computer to be a client for network
	  block devices, i.e. it will be able to use block devices exported by
	  servers (mount file systems on them etc.). Communication between
	  client and server works over TCP/IP networking, but to the client
	  program this is hidden: it looks like a regular local file access to
	  a block device special file such as /dev/nd0.

	  Network block devices also allows you to run a block-device in
	  userland (making server and client physically the same computer,
	  communicating using the loopback network device).

	  Read <file:Documentation/blockdev/nbd.txt> for more information,
	  especially about where to find the server code, which runs in user
	  space and does not need special kernel support.

	  Note that this has nothing to do with the network file systems NFS
	  or Coda; you can say N here even if you intend to use NFS or Coda.

	  To compile this driver as a module, choose M here: the
	  module will be called nbd.

	  If unsure, say N.

config BLK_DEV_SKD
	tristate "STEC S1120 Block Driver"
	depends on PCI
	depends on 64BIT
	---help---
	Saying Y or M here will enable support for the
	STEC, Inc. S1120 PCIe SSD.

	Use device /dev/skd$N amd /dev/skd$Np$M.

config BLK_DEV_SX8
	tristate "Promise SATA SX8 support"
	depends on PCI
	---help---
	  Saying Y or M here will enable support for the 
	  Promise SATA SX8 controllers.

	  Use devices /dev/sx8/$N and /dev/sx8/$Np$M.

config BLK_DEV_RAM
	tristate "RAM block device support"
	---help---
	  Saying Y here will allow you to use a portion of your RAM memory as
	  a block device, so that you can make file systems on it, read and
	  write to it and do all the other things that you can do with normal
	  block devices (such as hard drives). It is usually used to load and
	  store a copy of a minimal root file system off of a floppy into RAM
	  during the initial install of Linux.

	  Note that the kernel command line option "ramdisk=XX" is now obsolete.
	  For details, read <file:Documentation/blockdev/ramdisk.txt>.

	  To compile this driver as a module, choose M here: the
	  module will be called brd. An alias "rd" has been defined
	  for historical reasons.

	  Most normal users won't need the RAM disk functionality, and can
	  thus say N here.

config BLK_DEV_RAM_COUNT
	int "Default number of RAM disks"
	default "16"
	depends on BLK_DEV_RAM
	help
	  The default value is 16 RAM disks. Change this if you know what you
	  are doing. If you boot from a filesystem that needs to be extracted
	  in memory, you will need at least one RAM disk (e.g. root on cramfs).

config BLK_DEV_RAM_SIZE
	int "Default RAM disk size (kbytes)"
	depends on BLK_DEV_RAM
	default "4096"
	help
	  The default value is 4096 kilobytes. Only change this if you know
	  what you are doing.

config CDROM_PKTCDVD
	tristate "Packet writing on CD/DVD media (DEPRECATED)"
	depends on !UML
	select CDROM
	select BLK_SCSI_REQUEST
	help
	  Note: This driver is deprecated and will be removed from the
	  kernel in the near future!

	  If you have a CDROM/DVD drive that supports packet writing, say
	  Y to include support. It should work with any MMC/Mt Fuji
	  compliant ATAPI or SCSI drive, which is just about any newer
	  DVD/CD writer.

	  Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs
	  is possible.
	  DVD-RW disks must be in restricted overwrite mode.

	  See the file <file:Documentation/cdrom/packet-writing.txt>
	  for further information on the use of this driver.

	  To compile this driver as a module, choose M here: the
	  module will be called pktcdvd.

config CDROM_PKTCDVD_BUFFERS
	int "Free buffers for data gathering"
	depends on CDROM_PKTCDVD
	default "8"
	help
	  This controls the maximum number of active concurrent packets. More
	  concurrent packets can increase write performance, but also require
	  more memory. Each concurrent packet will require approximately 64Kb
	  of non-swappable kernel memory, memory which will be allocated when
	  a disc is opened for writing.

config CDROM_PKTCDVD_WCACHE
	bool "Enable write caching"
	depends on CDROM_PKTCDVD
	help
	  If enabled, write caching will be set for the CD-R/W device. For now
	  this option is dangerous unless the CD-RW media is known good, as we
	  don't do deferred write error handling yet.

config ATA_OVER_ETH
	tristate "ATA over Ethernet support"
	depends on NET
	help
	This driver provides Support for ATA over Ethernet block
	devices like the Coraid EtherDrive (R) Storage Blade.

config SUNVDC
	tristate "Sun Virtual Disk Client support"
	depends on SUN_LDOMS
	help
	  Support for virtual disk devices as a client under Sun
	  Logical Domains.

source "drivers/s390/block/Kconfig"

config XILINX_SYSACE
	tristate "Xilinx SystemACE support"
	depends on 4xx || MICROBLAZE
	help
	  Include support for the Xilinx SystemACE CompactFlash interface

config XEN_BLKDEV_FRONTEND
	tristate "Xen virtual block device support"
	depends on XEN
	default y
	select XEN_XENBUS_FRONTEND
	help
	  This driver implements the front-end of the Xen virtual
	  block device driver.  It communicates with a back-end driver
	  in another domain which drives the actual block device.

config XEN_BLKDEV_BACKEND
	tristate "Xen block-device backend driver"
	depends on XEN_BACKEND
	help
	  The block-device backend driver allows the kernel to export its
	  block devices to other guests via a high-performance shared-memory
	  interface.

	  The corresponding Linux frontend driver is enabled by the
	  CONFIG_XEN_BLKDEV_FRONTEND configuration option.

	  The backend driver attaches itself to a any block device specified
	  in the XenBus configuration. There are no limits to what the block
	  device as long as it has a major and minor.

	  If you are compiling a kernel to run in a Xen block backend driver
	  domain (often this is domain 0) you should say Y here. To
	  compile this driver as a module, chose M here: the module
	  will be called xen-blkback.


config VIRTIO_BLK
	tristate "Virtio block driver"
	depends on VIRTIO
	---help---
	  This is the virtual block driver for virtio.  It can be used with
          QEMU based VMMs (like KVM or Xen).  Say Y or M.

config VIRTIO_BLK_SCSI
	bool "SCSI passthrough request for the Virtio block driver"
	depends on VIRTIO_BLK
	select BLK_SCSI_REQUEST
	---help---
	  Enable support for SCSI passthrough (e.g. the SG_IO ioctl) on
	  virtio-blk devices.  This is only supported for the legacy
	  virtio protocol and not enabled by default by any hypervisor.
	  You probably want to use virtio-scsi instead.

config BLK_DEV_RBD
	tristate "Rados block device (RBD)"
	depends on INET && BLOCK
	select CEPH_LIB
	select LIBCRC32C
	select CRYPTO_AES
	select CRYPTO
	help
	  Say Y here if you want include the Rados block device, which stripes
	  a block device over objects stored in the Ceph distributed object
	  store.

	  More information at http://ceph.newdream.net/.

	  If unsure, say N.

config BLK_DEV_RSXX
	tristate "IBM Flash Adapter 900GB Full Height PCIe Device Driver"
	depends on PCI
	help
	  Device driver for IBM's high speed PCIe SSD
	  storage device: Flash Adapter 900GB Full Height.

	  To compile this driver as a module, choose M here: the
	  module will be called rsxx.

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