1 # SPDX-License-Identifier: GPL-2.0
3 # Block device driver configuration
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.
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.
19 config BLK_DEV_NULL_BLK
20 tristate "Null test block driver"
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
28 tristate "Normal floppy disk support"
29 depends on ARCH_MAY_HAVE_PC_FDC
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
33 Thinkpad users, is contained in
34 <file:Documentation/blockdev/floppy.txt>.
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.
39 To compile this driver as a module, choose M here: the
40 module will be called floppy.
42 config BLK_DEV_FD_RAWCMD
43 bool "Support for raw floppy disk commands (DEPRECATED)"
46 If you want to use actual physical floppies and expect to do
47 special low-level hardware accesses to them (access and use
48 non-standard formats, for example), then enable this.
50 Note that the code enabled by this option is rarely used and
51 might be unstable or insecure, and distros should not enable it.
53 Note: FDRAWCMD is deprecated and will be removed from the kernel
59 tristate "Amiga floppy support"
63 tristate "Atari floppy support"
67 tristate "Support for PowerMac floppy"
68 depends on PPC_PMAC && !PPC_PMAC64
70 If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
71 floppy controller, say Y here. Most commonly found in PowerMacs.
74 tristate "Support for SWIM Macintosh floppy"
75 depends on M68K && MAC
77 You should select this option if you want floppy support
78 and you don't have a II, IIfx, Q900, Q950 or AV series.
81 tristate "Amiga Zorro II ramdisk support"
84 This enables support for using Chip RAM and Zorro II RAM as a
85 ramdisk or as a swap partition. Say Y if you want to include this
88 To compile this driver as a module, choose M here: the
89 module will be called z2ram.
93 select BLK_SCSI_REQUEST
96 tristate "SEGA Dreamcast GD-ROM drive"
97 depends on SH_DREAMCAST
100 A standard SEGA Dreamcast comes with a modified CD ROM drive called a
101 "GD-ROM" by SEGA to signify it is capable of reading special disks
102 with up to 1 GB of data. This drive will also read standard CD ROM
103 disks. Select this option to access any disks in your GD ROM drive.
104 Most users will want to say "Y" here.
105 You can also build this as a module which will be called gdrom.
108 tristate "Parallel port IDE device support"
109 depends on PARPORT_PC
111 There are many external CD-ROM and disk devices that connect through
112 your computer's parallel port. Most of them are actually IDE devices
113 using a parallel port IDE adapter. This option enables the PARIDE
114 subsystem which contains drivers for many of these external drives.
115 Read <file:Documentation/blockdev/paride.txt> for more information.
117 If you have said Y to the "Parallel-port support" configuration
118 option, you may share a single port between your printer and other
119 parallel port devices. Answer Y to build PARIDE support into your
120 kernel, or M if you would like to build it as a loadable module. If
121 your parallel port support is in a loadable module, you must build
122 PARIDE as a module. If you built PARIDE support into your kernel,
123 you may still build the individual protocol modules and high-level
124 drivers as loadable modules. If you build this support as a module,
125 it will be called paride.
127 To use the PARIDE support, you must say Y or M here and also to at
128 least one high-level driver (e.g. "Parallel port IDE disks",
129 "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
130 to at least one protocol driver (e.g. "ATEN EH-100 protocol",
131 "MicroSolutions backpack protocol", "DataStor Commuter protocol"
134 source "drivers/block/paride/Kconfig"
136 source "drivers/block/mtip32xx/Kconfig"
138 source "drivers/block/zram/Kconfig"
140 config BLK_DEV_DAC960
141 tristate "Mylex DAC960/DAC1100 PCI RAID Controller support"
144 This driver adds support for the Mylex DAC960, AcceleRAID, and
145 eXtremeRAID PCI RAID controllers. See the file
146 <file:Documentation/blockdev/README.DAC960> for further information
149 To compile this driver as a module, choose M here: the
150 module will be called DAC960.
153 tristate "Micro Memory MM5415 Battery Backed RAM support"
156 Saying Y here will include support for the MM5415 family of
157 battery backed (Non-volatile) RAM cards.
158 <http://www.umem.com/>
160 The cards appear as block devices that can be partitioned into
161 as many as 15 partitions.
163 To compile this driver as a module, choose M here: the
164 module will be called umem.
166 The umem driver has not yet been allocated a MAJOR number, so
167 one is chosen dynamically.
170 bool "Virtual block device"
173 The User-Mode Linux port includes a driver called UBD which will let
174 you access arbitrary files on the host computer as block devices.
175 Unless you know that you do not need such virtual block devices say
178 config BLK_DEV_UBD_SYNC
179 bool "Always do synchronous disk IO for UBD"
180 depends on BLK_DEV_UBD
182 Writes to the virtual block device are not immediately written to the
183 host's disk; this may cause problems if, for example, the User-Mode
184 Linux 'Virtual Machine' uses a journalling filesystem and the host
187 Synchronous operation (i.e. always writing data to the host's disk
188 immediately) is configurable on a per-UBD basis by using a special
189 kernel command line option. Alternatively, you can say Y here to
190 turn on synchronous operation by default for all block devices.
192 If you're running a journalling file system (like reiserfs, for
193 example) in your virtual machine, you will want to say Y here. If
194 you care for the safety of the data in your virtual machine, Y is a
195 wise choice too. In all other cases (for example, if you're just
196 playing around with User-Mode Linux) you can choose N.
198 config BLK_DEV_COW_COMMON
203 tristate "Loopback device support"
205 Saying Y here will allow you to use a regular file as a block
206 device; you can then create a file system on that block device and
207 mount it just as you would mount other block devices such as hard
208 drive partitions, CD-ROM drives or floppy drives. The loop devices
209 are block special device files with major number 7 and typically
210 called /dev/loop0, /dev/loop1 etc.
212 This is useful if you want to check an ISO 9660 file system before
213 burning the CD, or if you want to use floppy images without first
214 writing them to floppy. Furthermore, some Linux distributions avoid
215 the need for a dedicated Linux partition by keeping their complete
216 root file system inside a DOS FAT file using this loop device
219 To use the loop device, you need the losetup utility, found in the
220 util-linux package, see
221 <https://www.kernel.org/pub/linux/utils/util-linux/>.
223 The loop device driver can also be used to "hide" a file system in
224 a disk partition, floppy, or regular file, either using encryption
225 (scrambling the data) or steganography (hiding the data in the low
226 bits of, say, a sound file). This is also safe if the file resides
227 on a remote file server.
229 There are several ways of encrypting disks. Some of these require
230 kernel patches. The vanilla kernel offers the cryptoloop option
231 and a Device Mapper target (which is superior, as it supports all
232 file systems). If you want to use the cryptoloop, say Y to both
233 LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12
234 or later) version of util-linux. Additionally, be aware that
235 the cryptoloop is not safe for storing journaled filesystems.
237 Note that this loop device has nothing to do with the loopback
238 device used for network connections from the machine to itself.
240 To compile this driver as a module, choose M here: the
241 module will be called loop.
243 Most users will answer N here.
245 config BLK_DEV_LOOP_MIN_COUNT
246 int "Number of loop devices to pre-create at init time"
247 depends on BLK_DEV_LOOP
250 Static number of loop devices to be unconditionally pre-created
253 This default value can be overwritten on the kernel command
254 line or with module-parameter loop.max_loop.
256 The historic default is 8. If a late 2011 version of losetup(8)
257 is used, it can be set to 0, since needed loop devices can be
258 dynamically allocated with the /dev/loop-control interface.
260 config BLK_DEV_CRYPTOLOOP
261 tristate "Cryptoloop Support (DEPRECATED)"
264 depends on BLK_DEV_LOOP
266 Say Y here if you want to be able to use the ciphers that are
267 provided by the CryptoAPI as loop transformation. This might be
268 used as hard disk encryption.
270 WARNING: This device is not safe for journaled file systems like
271 ext3 or Reiserfs. Please use the Device Mapper crypto module
272 instead, which can be configured to be on-disk compatible with the
273 cryptoloop device. cryptoloop support will be removed in Linux 5.16.
275 source "drivers/block/drbd/Kconfig"
278 tristate "Network block device support"
281 Saying Y here will allow your computer to be a client for network
282 block devices, i.e. it will be able to use block devices exported by
283 servers (mount file systems on them etc.). Communication between
284 client and server works over TCP/IP networking, but to the client
285 program this is hidden: it looks like a regular local file access to
286 a block device special file such as /dev/nd0.
288 Network block devices also allows you to run a block-device in
289 userland (making server and client physically the same computer,
290 communicating using the loopback network device).
292 Read <file:Documentation/blockdev/nbd.txt> for more information,
293 especially about where to find the server code, which runs in user
294 space and does not need special kernel support.
296 Note that this has nothing to do with the network file systems NFS
297 or Coda; you can say N here even if you intend to use NFS or Coda.
299 To compile this driver as a module, choose M here: the
300 module will be called nbd.
305 tristate "STEC S1120 Block Driver"
309 Saying Y or M here will enable support for the
310 STEC, Inc. S1120 PCIe SSD.
312 Use device /dev/skd$N amd /dev/skd$Np$M.
315 tristate "Promise SATA SX8 support"
318 Saying Y or M here will enable support for the
319 Promise SATA SX8 controllers.
321 Use devices /dev/sx8/$N and /dev/sx8/$Np$M.
324 tristate "RAM block device support"
326 Saying Y here will allow you to use a portion of your RAM memory as
327 a block device, so that you can make file systems on it, read and
328 write to it and do all the other things that you can do with normal
329 block devices (such as hard drives). It is usually used to load and
330 store a copy of a minimal root file system off of a floppy into RAM
331 during the initial install of Linux.
333 Note that the kernel command line option "ramdisk=XX" is now obsolete.
334 For details, read <file:Documentation/blockdev/ramdisk.txt>.
336 To compile this driver as a module, choose M here: the
337 module will be called brd. An alias "rd" has been defined
338 for historical reasons.
340 Most normal users won't need the RAM disk functionality, and can
343 config BLK_DEV_RAM_COUNT
344 int "Default number of RAM disks"
346 depends on BLK_DEV_RAM
348 The default value is 16 RAM disks. Change this if you know what you
349 are doing. If you boot from a filesystem that needs to be extracted
350 in memory, you will need at least one RAM disk (e.g. root on cramfs).
352 config BLK_DEV_RAM_SIZE
353 int "Default RAM disk size (kbytes)"
354 depends on BLK_DEV_RAM
357 The default value is 4096 kilobytes. Only change this if you know
361 tristate "Packet writing on CD/DVD media (DEPRECATED)"
364 select BLK_SCSI_REQUEST
366 Note: This driver is deprecated and will be removed from the
367 kernel in the near future!
369 If you have a CDROM/DVD drive that supports packet writing, say
370 Y to include support. It should work with any MMC/Mt Fuji
371 compliant ATAPI or SCSI drive, which is just about any newer
374 Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs
376 DVD-RW disks must be in restricted overwrite mode.
378 See the file <file:Documentation/cdrom/packet-writing.txt>
379 for further information on the use of this driver.
381 To compile this driver as a module, choose M here: the
382 module will be called pktcdvd.
384 config CDROM_PKTCDVD_BUFFERS
385 int "Free buffers for data gathering"
386 depends on CDROM_PKTCDVD
389 This controls the maximum number of active concurrent packets. More
390 concurrent packets can increase write performance, but also require
391 more memory. Each concurrent packet will require approximately 64Kb
392 of non-swappable kernel memory, memory which will be allocated when
393 a disc is opened for writing.
395 config CDROM_PKTCDVD_WCACHE
396 bool "Enable write caching"
397 depends on CDROM_PKTCDVD
399 If enabled, write caching will be set for the CD-R/W device. For now
400 this option is dangerous unless the CD-RW media is known good, as we
401 don't do deferred write error handling yet.
404 tristate "ATA over Ethernet support"
407 This driver provides Support for ATA over Ethernet block
408 devices like the Coraid EtherDrive (R) Storage Blade.
411 tristate "Sun Virtual Disk Client support"
414 Support for virtual disk devices as a client under Sun
417 source "drivers/s390/block/Kconfig"
420 tristate "Xilinx SystemACE support"
421 depends on 4xx || MICROBLAZE
423 Include support for the Xilinx SystemACE CompactFlash interface
425 config XEN_BLKDEV_FRONTEND
426 tristate "Xen virtual block device support"
429 select XEN_XENBUS_FRONTEND
431 This driver implements the front-end of the Xen virtual
432 block device driver. It communicates with a back-end driver
433 in another domain which drives the actual block device.
435 config XEN_BLKDEV_BACKEND
436 tristate "Xen block-device backend driver"
437 depends on XEN_BACKEND
439 The block-device backend driver allows the kernel to export its
440 block devices to other guests via a high-performance shared-memory
443 The corresponding Linux frontend driver is enabled by the
444 CONFIG_XEN_BLKDEV_FRONTEND configuration option.
446 The backend driver attaches itself to a any block device specified
447 in the XenBus configuration. There are no limits to what the block
448 device as long as it has a major and minor.
450 If you are compiling a kernel to run in a Xen block backend driver
451 domain (often this is domain 0) you should say Y here. To
452 compile this driver as a module, chose M here: the module
453 will be called xen-blkback.
457 tristate "Virtio block driver"
460 This is the virtual block driver for virtio. It can be used with
461 QEMU based VMMs (like KVM or Xen). Say Y or M.
463 config VIRTIO_BLK_SCSI
464 bool "SCSI passthrough request for the Virtio block driver"
465 depends on VIRTIO_BLK
466 select BLK_SCSI_REQUEST
468 Enable support for SCSI passthrough (e.g. the SG_IO ioctl) on
469 virtio-blk devices. This is only supported for the legacy
470 virtio protocol and not enabled by default by any hypervisor.
471 You probably want to use virtio-scsi instead.
474 tristate "Rados block device (RBD)"
475 depends on INET && BLOCK
482 Say Y here if you want include the Rados block device, which stripes
483 a block device over objects stored in the Ceph distributed object
486 More information at http://ceph.newdream.net/.
491 tristate "IBM Flash Adapter 900GB Full Height PCIe Device Driver"
495 Device driver for IBM's high speed PCIe SSD
496 storage device: Flash Adapter 900GB Full Height.
498 To compile this driver as a module, choose M here: the
499 module will be called rsxx.