2 # Block device driver configuration
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.
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.
18 config BLK_DEV_NULL_BLK
19 tristate "Null test block driver"
20 depends on CONFIGFS_FS
23 tristate "Normal floppy disk support"
24 depends on ARCH_MAY_HAVE_PC_FDC
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.
34 To compile this driver as a module, choose M here: the
35 module will be called floppy.
38 tristate "Amiga floppy support"
42 tristate "Atari floppy support"
46 tristate "Support for PowerMac floppy"
47 depends on PPC_PMAC && !PPC_PMAC64
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.
53 tristate "Support for SWIM Macintosh floppy"
54 depends on M68K && MAC
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.
60 tristate "Amiga Zorro II ramdisk support"
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
67 To compile this driver as a module, choose M here: the
68 module will be called z2ram.
71 tristate "SEGA Dreamcast GD-ROM drive"
72 depends on SH_DREAMCAST
73 select BLK_SCSI_REQUEST # only for the generic cdrom code
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.
83 tristate "Parallel port IDE device support"
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.
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.
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"
109 source "drivers/block/paride/Kconfig"
111 source "drivers/block/mtip32xx/Kconfig"
113 source "drivers/block/zram/Kconfig"
115 config BLK_CPQ_CISS_DA
116 tristate "Compaq Smart Array 5xxx support"
118 select CHECK_SIGNATURE
119 select BLK_SCSI_REQUEST
121 This is the driver for Compaq Smart Array 5xxx controllers.
122 Everyone using these boards should say Y here.
123 See <file:Documentation/blockdev/cciss.txt> for the current list of
124 boards supported by this driver, and for further information
125 on the use of this driver.
127 config CISS_SCSI_TAPE
128 bool "SCSI tape drive support for Smart Array 5xxx"
129 depends on BLK_CPQ_CISS_DA && PROC_FS
130 depends on SCSI=y || SCSI=BLK_CPQ_CISS_DA
132 When enabled (Y), this option allows SCSI tape drives and SCSI medium
133 changers (tape robots) to be accessed via a Compaq 5xxx array
134 controller. (See <file:Documentation/blockdev/cciss.txt> for more details.)
136 "SCSI support" and "SCSI tape support" must also be enabled for this
139 When this option is disabled (N), the SCSI portion of the driver
142 config BLK_DEV_DAC960
143 tristate "Mylex DAC960/DAC1100 PCI RAID Controller support"
146 This driver adds support for the Mylex DAC960, AcceleRAID, and
147 eXtremeRAID PCI RAID controllers. See the file
148 <file:Documentation/blockdev/README.DAC960> for further information
151 To compile this driver as a module, choose M here: the
152 module will be called DAC960.
155 tristate "Micro Memory MM5415 Battery Backed RAM support"
158 Saying Y here will include support for the MM5415 family of
159 battery backed (Non-volatile) RAM cards.
160 <http://www.umem.com/>
162 The cards appear as block devices that can be partitioned into
163 as many as 15 partitions.
165 To compile this driver as a module, choose M here: the
166 module will be called umem.
168 The umem driver has not yet been allocated a MAJOR number, so
169 one is chosen dynamically.
172 bool "Virtual block device"
175 The User-Mode Linux port includes a driver called UBD which will let
176 you access arbitrary files on the host computer as block devices.
177 Unless you know that you do not need such virtual block devices say
180 config BLK_DEV_UBD_SYNC
181 bool "Always do synchronous disk IO for UBD"
182 depends on BLK_DEV_UBD
184 Writes to the virtual block device are not immediately written to the
185 host's disk; this may cause problems if, for example, the User-Mode
186 Linux 'Virtual Machine' uses a journalling filesystem and the host
189 Synchronous operation (i.e. always writing data to the host's disk
190 immediately) is configurable on a per-UBD basis by using a special
191 kernel command line option. Alternatively, you can say Y here to
192 turn on synchronous operation by default for all block devices.
194 If you're running a journalling file system (like reiserfs, for
195 example) in your virtual machine, you will want to say Y here. If
196 you care for the safety of the data in your virtual machine, Y is a
197 wise choice too. In all other cases (for example, if you're just
198 playing around with User-Mode Linux) you can choose N.
200 config BLK_DEV_COW_COMMON
205 tristate "Loopback device support"
207 Saying Y here will allow you to use a regular file as a block
208 device; you can then create a file system on that block device and
209 mount it just as you would mount other block devices such as hard
210 drive partitions, CD-ROM drives or floppy drives. The loop devices
211 are block special device files with major number 7 and typically
212 called /dev/loop0, /dev/loop1 etc.
214 This is useful if you want to check an ISO 9660 file system before
215 burning the CD, or if you want to use floppy images without first
216 writing them to floppy. Furthermore, some Linux distributions avoid
217 the need for a dedicated Linux partition by keeping their complete
218 root file system inside a DOS FAT file using this loop device
221 To use the loop device, you need the losetup utility, found in the
222 util-linux package, see
223 <https://www.kernel.org/pub/linux/utils/util-linux/>.
225 The loop device driver can also be used to "hide" a file system in
226 a disk partition, floppy, or regular file, either using encryption
227 (scrambling the data) or steganography (hiding the data in the low
228 bits of, say, a sound file). This is also safe if the file resides
229 on a remote file server.
231 There are several ways of encrypting disks. Some of these require
232 kernel patches. The vanilla kernel offers the cryptoloop option
233 and a Device Mapper target (which is superior, as it supports all
234 file systems). If you want to use the cryptoloop, say Y to both
235 LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12
236 or later) version of util-linux. Additionally, be aware that
237 the cryptoloop is not safe for storing journaled filesystems.
239 Note that this loop device has nothing to do with the loopback
240 device used for network connections from the machine to itself.
242 To compile this driver as a module, choose M here: the
243 module will be called loop.
245 Most users will answer N here.
247 config BLK_DEV_LOOP_MIN_COUNT
248 int "Number of loop devices to pre-create at init time"
249 depends on BLK_DEV_LOOP
252 Static number of loop devices to be unconditionally pre-created
255 This default value can be overwritten on the kernel command
256 line or with module-parameter loop.max_loop.
258 The historic default is 8. If a late 2011 version of losetup(8)
259 is used, it can be set to 0, since needed loop devices can be
260 dynamically allocated with the /dev/loop-control interface.
262 config BLK_DEV_CRYPTOLOOP
263 tristate "Cryptoloop Support"
266 depends on BLK_DEV_LOOP
268 Say Y here if you want to be able to use the ciphers that are
269 provided by the CryptoAPI as loop transformation. This might be
270 used as hard disk encryption.
272 WARNING: This device is not safe for journaled file systems like
273 ext3 or Reiserfs. Please use the Device Mapper crypto module
274 instead, which can be configured to be on-disk compatible with the
277 source "drivers/block/drbd/Kconfig"
280 tristate "Network block device support"
283 Saying Y here will allow your computer to be a client for network
284 block devices, i.e. it will be able to use block devices exported by
285 servers (mount file systems on them etc.). Communication between
286 client and server works over TCP/IP networking, but to the client
287 program this is hidden: it looks like a regular local file access to
288 a block device special file such as /dev/nd0.
290 Network block devices also allows you to run a block-device in
291 userland (making server and client physically the same computer,
292 communicating using the loopback network device).
294 Read <file:Documentation/blockdev/nbd.txt> for more information,
295 especially about where to find the server code, which runs in user
296 space and does not need special kernel support.
298 Note that this has nothing to do with the network file systems NFS
299 or Coda; you can say N here even if you intend to use NFS or Coda.
301 To compile this driver as a module, choose M here: the
302 module will be called nbd.
307 tristate "STEC S1120 Block Driver"
311 Saying Y or M here will enable support for the
312 STEC, Inc. S1120 PCIe SSD.
314 Use device /dev/skd$N amd /dev/skd$Np$M.
317 tristate "Promise SATA SX8 support"
320 Saying Y or M here will enable support for the
321 Promise SATA SX8 controllers.
323 Use devices /dev/sx8/$N and /dev/sx8/$Np$M.
326 tristate "RAM block device support"
327 select DAX if BLK_DEV_RAM_DAX
329 Saying Y here will allow you to use a portion of your RAM memory as
330 a block device, so that you can make file systems on it, read and
331 write to it and do all the other things that you can do with normal
332 block devices (such as hard drives). It is usually used to load and
333 store a copy of a minimal root file system off of a floppy into RAM
334 during the initial install of Linux.
336 Note that the kernel command line option "ramdisk=XX" is now obsolete.
337 For details, read <file:Documentation/blockdev/ramdisk.txt>.
339 To compile this driver as a module, choose M here: the
340 module will be called brd. An alias "rd" has been defined
341 for historical reasons.
343 Most normal users won't need the RAM disk functionality, and can
346 config BLK_DEV_RAM_COUNT
347 int "Default number of RAM disks"
349 depends on BLK_DEV_RAM
351 The default value is 16 RAM disks. Change this if you know what you
352 are doing. If you boot from a filesystem that needs to be extracted
353 in memory, you will need at least one RAM disk (e.g. root on cramfs).
355 config BLK_DEV_RAM_SIZE
356 int "Default RAM disk size (kbytes)"
357 depends on BLK_DEV_RAM
360 The default value is 4096 kilobytes. Only change this if you know
363 config BLK_DEV_RAM_DAX
364 bool "Support Direct Access (DAX) to RAM block devices"
365 depends on BLK_DEV_RAM && FS_DAX
368 Support filesystems using DAX to access RAM block devices. This
369 avoids double-buffering data in the page cache before copying it
370 to the block device. Answering Y will slightly enlarge the kernel,
371 and will prevent RAM block device backing store memory from being
372 allocated from highmem (only a problem for highmem systems).
375 tristate "Packet writing on CD/DVD media (DEPRECATED)"
377 select BLK_SCSI_REQUEST
379 Note: This driver is deprecated and will be removed from the
380 kernel in the near future!
382 If you have a CDROM/DVD drive that supports packet writing, say
383 Y to include support. It should work with any MMC/Mt Fuji
384 compliant ATAPI or SCSI drive, which is just about any newer
387 Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs
389 DVD-RW disks must be in restricted overwrite mode.
391 See the file <file:Documentation/cdrom/packet-writing.txt>
392 for further information on the use of this driver.
394 To compile this driver as a module, choose M here: the
395 module will be called pktcdvd.
397 config CDROM_PKTCDVD_BUFFERS
398 int "Free buffers for data gathering"
399 depends on CDROM_PKTCDVD
402 This controls the maximum number of active concurrent packets. More
403 concurrent packets can increase write performance, but also require
404 more memory. Each concurrent packet will require approximately 64Kb
405 of non-swappable kernel memory, memory which will be allocated when
406 a disc is opened for writing.
408 config CDROM_PKTCDVD_WCACHE
409 bool "Enable write caching"
410 depends on CDROM_PKTCDVD
412 If enabled, write caching will be set for the CD-R/W device. For now
413 this option is dangerous unless the CD-RW media is known good, as we
414 don't do deferred write error handling yet.
417 tristate "ATA over Ethernet support"
420 This driver provides Support for ATA over Ethernet block
421 devices like the Coraid EtherDrive (R) Storage Blade.
424 tristate "Sun Virtual Disk Client support"
427 Support for virtual disk devices as a client under Sun
430 source "drivers/s390/block/Kconfig"
433 tristate "Xilinx SystemACE support"
434 depends on 4xx || MICROBLAZE
436 Include support for the Xilinx SystemACE CompactFlash interface
438 config XEN_BLKDEV_FRONTEND
439 tristate "Xen virtual block device support"
442 select XEN_XENBUS_FRONTEND
444 This driver implements the front-end of the Xen virtual
445 block device driver. It communicates with a back-end driver
446 in another domain which drives the actual block device.
448 config XEN_BLKDEV_BACKEND
449 tristate "Xen block-device backend driver"
450 depends on XEN_BACKEND
452 The block-device backend driver allows the kernel to export its
453 block devices to other guests via a high-performance shared-memory
456 The corresponding Linux frontend driver is enabled by the
457 CONFIG_XEN_BLKDEV_FRONTEND configuration option.
459 The backend driver attaches itself to a any block device specified
460 in the XenBus configuration. There are no limits to what the block
461 device as long as it has a major and minor.
463 If you are compiling a kernel to run in a Xen block backend driver
464 domain (often this is domain 0) you should say Y here. To
465 compile this driver as a module, chose M here: the module
466 will be called xen-blkback.
470 tristate "Virtio block driver"
473 This is the virtual block driver for virtio. It can be used with
474 QEMU based VMMs (like KVM or Xen). Say Y or M.
476 config VIRTIO_BLK_SCSI
477 bool "SCSI passthrough request for the Virtio block driver"
478 depends on VIRTIO_BLK
479 select BLK_SCSI_REQUEST
481 Enable support for SCSI passthrough (e.g. the SG_IO ioctl) on
482 virtio-blk devices. This is only supported for the legacy
483 virtio protocol and not enabled by default by any hypervisor.
484 You probably want to use virtio-scsi instead.
487 tristate "Rados block device (RBD)"
488 depends on INET && BLOCK
495 Say Y here if you want include the Rados block device, which stripes
496 a block device over objects stored in the Ceph distributed object
499 More information at http://ceph.newdream.net/.
504 tristate "IBM Flash Adapter 900GB Full Height PCIe Device Driver"
507 Device driver for IBM's high speed PCIe SSD
508 storage device: Flash Adapter 900GB Full Height.
510 To compile this driver as a module, choose M here: the
511 module will be called rsxx.