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"
22 tristate "Normal floppy disk support"
23 depends on ARCH_MAY_HAVE_PC_FDC
25 If you want to use the floppy disk drive(s) of your PC under Linux,
26 say Y. Information about this driver, especially important for IBM
27 Thinkpad users, is contained in
28 <file:Documentation/blockdev/floppy.txt>.
29 That file also contains the location of the Floppy driver FAQ as
30 well as location of the fdutils package used to configure additional
31 parameters of the driver at run time.
33 To compile this driver as a module, choose M here: the
34 module will be called floppy.
37 tristate "Amiga floppy support"
41 tristate "Atari floppy support"
45 tristate "Support for PowerMac floppy"
46 depends on PPC_PMAC && !PPC_PMAC64
48 If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
49 floppy controller, say Y here. Most commonly found in PowerMacs.
52 tristate "Support for SWIM Macintosh floppy"
53 depends on M68K && MAC
55 You should select this option if you want floppy support
56 and you don't have a II, IIfx, Q900, Q950 or AV series.
59 tristate "Amiga Zorro II ramdisk support"
62 This enables support for using Chip RAM and Zorro II RAM as a
63 ramdisk or as a swap partition. Say Y if you want to include this
66 To compile this driver as a module, choose M here: the
67 module will be called z2ram.
70 tristate "SEGA Dreamcast GD-ROM drive"
71 depends on SH_DREAMCAST
73 A standard SEGA Dreamcast comes with a modified CD ROM drive called a
74 "GD-ROM" by SEGA to signify it is capable of reading special disks
75 with up to 1 GB of data. This drive will also read standard CD ROM
76 disks. Select this option to access any disks in your GD ROM drive.
77 Most users will want to say "Y" here.
78 You can also build this as a module which will be called gdrom.
81 tristate "Parallel port IDE device support"
84 There are many external CD-ROM and disk devices that connect through
85 your computer's parallel port. Most of them are actually IDE devices
86 using a parallel port IDE adapter. This option enables the PARIDE
87 subsystem which contains drivers for many of these external drives.
88 Read <file:Documentation/blockdev/paride.txt> for more information.
90 If you have said Y to the "Parallel-port support" configuration
91 option, you may share a single port between your printer and other
92 parallel port devices. Answer Y to build PARIDE support into your
93 kernel, or M if you would like to build it as a loadable module. If
94 your parallel port support is in a loadable module, you must build
95 PARIDE as a module. If you built PARIDE support into your kernel,
96 you may still build the individual protocol modules and high-level
97 drivers as loadable modules. If you build this support as a module,
98 it will be called paride.
100 To use the PARIDE support, you must say Y or M here and also to at
101 least one high-level driver (e.g. "Parallel port IDE disks",
102 "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
103 to at least one protocol driver (e.g. "ATEN EH-100 protocol",
104 "MicroSolutions backpack protocol", "DataStor Commuter protocol"
107 source "drivers/block/paride/Kconfig"
109 source "drivers/block/mtip32xx/Kconfig"
112 tristate "Compaq SMART2 support"
113 depends on PCI && VIRT_TO_BUS && 0
115 This is the driver for Compaq Smart Array controllers. Everyone
116 using these boards should say Y here. See the file
117 <file:Documentation/blockdev/cpqarray.txt> for the current list of
118 boards supported by this driver, and for further information on the
121 config BLK_CPQ_CISS_DA
122 tristate "Compaq Smart Array 5xxx support"
124 select CHECK_SIGNATURE
126 This is the driver for Compaq Smart Array 5xxx controllers.
127 Everyone using these boards should say Y here.
128 See <file:Documentation/blockdev/cciss.txt> for the current list of
129 boards supported by this driver, and for further information
130 on the use of this driver.
132 config CISS_SCSI_TAPE
133 bool "SCSI tape drive support for Smart Array 5xxx"
134 depends on BLK_CPQ_CISS_DA && PROC_FS
135 depends on SCSI=y || SCSI=BLK_CPQ_CISS_DA
137 When enabled (Y), this option allows SCSI tape drives and SCSI medium
138 changers (tape robots) to be accessed via a Compaq 5xxx array
139 controller. (See <file:Documentation/blockdev/cciss.txt> for more details.)
141 "SCSI support" and "SCSI tape support" must also be enabled for this
144 When this option is disabled (N), the SCSI portion of the driver
147 config BLK_DEV_DAC960
148 tristate "Mylex DAC960/DAC1100 PCI RAID Controller support"
151 This driver adds support for the Mylex DAC960, AcceleRAID, and
152 eXtremeRAID PCI RAID controllers. See the file
153 <file:Documentation/blockdev/README.DAC960> for further information
156 To compile this driver as a module, choose M here: the
157 module will be called DAC960.
160 tristate "Micro Memory MM5415 Battery Backed RAM support"
163 Saying Y here will include support for the MM5415 family of
164 battery backed (Non-volatile) RAM cards.
165 <http://www.umem.com/>
167 The cards appear as block devices that can be partitioned into
168 as many as 15 partitions.
170 To compile this driver as a module, choose M here: the
171 module will be called umem.
173 The umem driver has not yet been allocated a MAJOR number, so
174 one is chosen dynamically.
177 bool "Virtual block device"
180 The User-Mode Linux port includes a driver called UBD which will let
181 you access arbitrary files on the host computer as block devices.
182 Unless you know that you do not need such virtual block devices say
185 config BLK_DEV_UBD_SYNC
186 bool "Always do synchronous disk IO for UBD"
187 depends on BLK_DEV_UBD
189 Writes to the virtual block device are not immediately written to the
190 host's disk; this may cause problems if, for example, the User-Mode
191 Linux 'Virtual Machine' uses a journalling filesystem and the host
194 Synchronous operation (i.e. always writing data to the host's disk
195 immediately) is configurable on a per-UBD basis by using a special
196 kernel command line option. Alternatively, you can say Y here to
197 turn on synchronous operation by default for all block devices.
199 If you're running a journalling file system (like reiserfs, for
200 example) in your virtual machine, you will want to say Y here. If
201 you care for the safety of the data in your virtual machine, Y is a
202 wise choice too. In all other cases (for example, if you're just
203 playing around with User-Mode Linux) you can choose N.
205 config BLK_DEV_COW_COMMON
210 tristate "Loopback device support"
212 Saying Y here will allow you to use a regular file as a block
213 device; you can then create a file system on that block device and
214 mount it just as you would mount other block devices such as hard
215 drive partitions, CD-ROM drives or floppy drives. The loop devices
216 are block special device files with major number 7 and typically
217 called /dev/loop0, /dev/loop1 etc.
219 This is useful if you want to check an ISO 9660 file system before
220 burning the CD, or if you want to use floppy images without first
221 writing them to floppy. Furthermore, some Linux distributions avoid
222 the need for a dedicated Linux partition by keeping their complete
223 root file system inside a DOS FAT file using this loop device
226 To use the loop device, you need the losetup utility, found in the
227 util-linux package, see
228 <ftp://ftp.kernel.org/pub/linux/utils/util-linux/>.
230 The loop device driver can also be used to "hide" a file system in
231 a disk partition, floppy, or regular file, either using encryption
232 (scrambling the data) or steganography (hiding the data in the low
233 bits of, say, a sound file). This is also safe if the file resides
234 on a remote file server.
236 There are several ways of encrypting disks. Some of these require
237 kernel patches. The vanilla kernel offers the cryptoloop option
238 and a Device Mapper target (which is superior, as it supports all
239 file systems). If you want to use the cryptoloop, say Y to both
240 LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12
241 or later) version of util-linux. Additionally, be aware that
242 the cryptoloop is not safe for storing journaled filesystems.
244 Note that this loop device has nothing to do with the loopback
245 device used for network connections from the machine to itself.
247 To compile this driver as a module, choose M here: the
248 module will be called loop.
250 Most users will answer N here.
252 config BLK_DEV_LOOP_MIN_COUNT
253 int "Number of loop devices to pre-create at init time"
254 depends on BLK_DEV_LOOP
257 Static number of loop devices to be unconditionally pre-created
260 This default value can be overwritten on the kernel command
261 line or with module-parameter loop.max_loop.
263 The historic default is 8. If a late 2011 version of losetup(8)
264 is used, it can be set to 0, since needed loop devices can be
265 dynamically allocated with the /dev/loop-control interface.
267 config BLK_DEV_CRYPTOLOOP
268 tristate "Cryptoloop Support"
271 depends on BLK_DEV_LOOP
273 Say Y here if you want to be able to use the ciphers that are
274 provided by the CryptoAPI as loop transformation. This might be
275 used as hard disk encryption.
277 WARNING: This device is not safe for journaled file systems like
278 ext3 or Reiserfs. Please use the Device Mapper crypto module
279 instead, which can be configured to be on-disk compatible with the
282 source "drivers/block/drbd/Kconfig"
285 tristate "Network block device support"
288 Saying Y here will allow your computer to be a client for network
289 block devices, i.e. it will be able to use block devices exported by
290 servers (mount file systems on them etc.). Communication between
291 client and server works over TCP/IP networking, but to the client
292 program this is hidden: it looks like a regular local file access to
293 a block device special file such as /dev/nd0.
295 Network block devices also allows you to run a block-device in
296 userland (making server and client physically the same computer,
297 communicating using the loopback network device).
299 Read <file:Documentation/blockdev/nbd.txt> for more information,
300 especially about where to find the server code, which runs in user
301 space and does not need special kernel support.
303 Note that this has nothing to do with the network file systems NFS
304 or Coda; you can say N here even if you intend to use NFS or Coda.
306 To compile this driver as a module, choose M here: the
307 module will be called nbd.
312 tristate "NVM Express block device"
315 The NVM Express driver is for solid state drives directly
316 connected to the PCI or PCI Express bus. If you know you
317 don't have one of these, it is safe to answer N.
319 To compile this driver as a module, choose M here: the
320 module will be called nvme.
323 tristate "STEC S1120 Block Driver"
327 Saying Y or M here will enable support for the
328 STEC, Inc. S1120 PCIe SSD.
330 Use device /dev/skd$N amd /dev/skd$Np$M.
333 tristate "OSD object-as-blkdev support"
334 depends on SCSI_OSD_ULD
336 Saying Y or M here will allow the exporting of a single SCSI
337 OSD (object-based storage) object as a Linux block device.
339 For example, if you create a 2G object on an OSD device,
340 you can then use this module to present that 2G object as
341 a Linux block device.
343 To compile this driver as a module, choose M here: the
344 module will be called osdblk.
349 tristate "Promise SATA SX8 support"
352 Saying Y or M here will enable support for the
353 Promise SATA SX8 controllers.
355 Use devices /dev/sx8/$N and /dev/sx8/$Np$M.
358 tristate "RAM block device support"
360 Saying Y here will allow you to use a portion of your RAM memory as
361 a block device, so that you can make file systems on it, read and
362 write to it and do all the other things that you can do with normal
363 block devices (such as hard drives). It is usually used to load and
364 store a copy of a minimal root file system off of a floppy into RAM
365 during the initial install of Linux.
367 Note that the kernel command line option "ramdisk=XX" is now obsolete.
368 For details, read <file:Documentation/blockdev/ramdisk.txt>.
370 To compile this driver as a module, choose M here: the
371 module will be called rd.
373 Most normal users won't need the RAM disk functionality, and can
376 config BLK_DEV_RAM_COUNT
377 int "Default number of RAM disks"
379 depends on BLK_DEV_RAM
381 The default value is 16 RAM disks. Change this if you know what you
382 are doing. If you boot from a filesystem that needs to be extracted
383 in memory, you will need at least one RAM disk (e.g. root on cramfs).
385 config BLK_DEV_RAM_SIZE
386 int "Default RAM disk size (kbytes)"
387 depends on BLK_DEV_RAM
390 The default value is 4096 kilobytes. Only change this if you know
394 bool "Support XIP filesystems on RAM block device"
395 depends on BLK_DEV_RAM
398 Support XIP filesystems (such as ext2 with XIP support on) on
399 top of block ram device. This will slightly enlarge the kernel, and
400 will prevent RAM block device backing store memory from being
401 allocated from highmem (only a problem for highmem systems).
404 tristate "Packet writing on CD/DVD media"
407 If you have a CDROM/DVD drive that supports packet writing, say
408 Y to include support. It should work with any MMC/Mt Fuji
409 compliant ATAPI or SCSI drive, which is just about any newer
412 Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs
414 DVD-RW disks must be in restricted overwrite mode.
416 See the file <file:Documentation/cdrom/packet-writing.txt>
417 for further information on the use of this driver.
419 To compile this driver as a module, choose M here: the
420 module will be called pktcdvd.
422 config CDROM_PKTCDVD_BUFFERS
423 int "Free buffers for data gathering"
424 depends on CDROM_PKTCDVD
427 This controls the maximum number of active concurrent packets. More
428 concurrent packets can increase write performance, but also require
429 more memory. Each concurrent packet will require approximately 64Kb
430 of non-swappable kernel memory, memory which will be allocated when
431 a disc is opened for writing.
433 config CDROM_PKTCDVD_WCACHE
434 bool "Enable write caching"
435 depends on CDROM_PKTCDVD
437 If enabled, write caching will be set for the CD-R/W device. For now
438 this option is dangerous unless the CD-RW media is known good, as we
439 don't do deferred write error handling yet.
442 tristate "ATA over Ethernet support"
445 This driver provides Support for ATA over Ethernet block
446 devices like the Coraid EtherDrive (R) Storage Blade.
449 tristate "mGine mflash, gflash support"
450 depends on ARM && GPIOLIB
452 mGine mFlash(gFlash) block device driver
455 int "Size of reserved area before MBR"
459 Define size of reserved area that usually used for boot. Unit is KB.
460 All of the block device operation will be taken this value as start
466 tristate "Sun Virtual Disk Client support"
469 Support for virtual disk devices as a client under Sun
472 source "drivers/s390/block/Kconfig"
475 tristate "Xilinx SystemACE support"
476 depends on 4xx || MICROBLAZE
478 Include support for the Xilinx SystemACE CompactFlash interface
480 config XEN_BLKDEV_FRONTEND
481 tristate "Xen virtual block device support"
484 select XEN_XENBUS_FRONTEND
486 This driver implements the front-end of the Xen virtual
487 block device driver. It communicates with a back-end driver
488 in another domain which drives the actual block device.
490 config XEN_BLKDEV_BACKEND
491 tristate "Xen block-device backend driver"
492 depends on XEN_BACKEND
494 The block-device backend driver allows the kernel to export its
495 block devices to other guests via a high-performance shared-memory
498 The corresponding Linux frontend driver is enabled by the
499 CONFIG_XEN_BLKDEV_FRONTEND configuration option.
501 The backend driver attaches itself to a any block device specified
502 in the XenBus configuration. There are no limits to what the block
503 device as long as it has a major and minor.
505 If you are compiling a kernel to run in a Xen block backend driver
506 domain (often this is domain 0) you should say Y here. To
507 compile this driver as a module, chose M here: the module
508 will be called xen-blkback.
512 tristate "Virtio block driver"
515 This is the virtual block driver for virtio. It can be used with
516 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
519 bool "Very old hard disk (MFM/RLL/IDE) driver"
521 depends on !ARM || ARCH_RPC || BROKEN
523 This is a very old hard disk driver that lacks the enhanced
524 functionality of the newer ones.
526 It is required for systems with ancient MFM/RLL/ESDI drives.
531 tristate "Rados block device (RBD)"
532 depends on INET && BLOCK
539 Say Y here if you want include the Rados block device, which stripes
540 a block device over objects stored in the Ceph distributed object
543 More information at http://ceph.newdream.net/.
548 tristate "IBM Flash Adapter 900GB Full Height PCIe Device Driver"
551 Device driver for IBM's high speed PCIe SSD
552 storage device: Flash Adapter 900GB Full Height.
554 To compile this driver as a module, choose M here: the
555 module will be called rsxx.