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"
24 tristate "Normal floppy disk support"
25 depends on ARCH_MAY_HAVE_PC_FDC
27 If you want to use the floppy disk drive(s) of your PC under Linux,
28 say Y. Information about this driver, especially important for IBM
29 Thinkpad users, is contained in
30 <file:Documentation/blockdev/floppy.txt>.
31 That file also contains the location of the Floppy driver FAQ as
32 well as location of the fdutils package used to configure additional
33 parameters of the driver at run time.
35 To compile this driver as a module, choose M here: the
36 module will be called floppy.
38 config BLK_DEV_FD_RAWCMD
39 bool "Support for raw floppy disk commands (DEPRECATED)"
42 If you want to use actual physical floppies and expect to do
43 special low-level hardware accesses to them (access and use
44 non-standard formats, for example), then enable this.
46 Note that the code enabled by this option is rarely used and
47 might be unstable or insecure, and distros should not enable it.
49 Note: FDRAWCMD is deprecated and will be removed from the kernel
55 tristate "Amiga floppy support"
59 tristate "Atari floppy support"
63 tristate "Support for PowerMac floppy"
64 depends on PPC_PMAC && !PPC_PMAC64
66 If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
67 floppy controller, say Y here. Most commonly found in PowerMacs.
70 tristate "Support for SWIM Macintosh floppy"
71 depends on M68K && MAC
73 You should select this option if you want floppy support
74 and you don't have a II, IIfx, Q900, Q950 or AV series.
77 tristate "Amiga Zorro II ramdisk support"
80 This enables support for using Chip RAM and Zorro II RAM as a
81 ramdisk or as a swap partition. Say Y if you want to include this
84 To compile this driver as a module, choose M here: the
85 module will be called z2ram.
88 tristate "SEGA Dreamcast GD-ROM drive"
89 depends on SH_DREAMCAST
90 select BLK_SCSI_REQUEST # only for the generic cdrom code
92 A standard SEGA Dreamcast comes with a modified CD ROM drive called a
93 "GD-ROM" by SEGA to signify it is capable of reading special disks
94 with up to 1 GB of data. This drive will also read standard CD ROM
95 disks. Select this option to access any disks in your GD ROM drive.
96 Most users will want to say "Y" here.
97 You can also build this as a module which will be called gdrom.
100 tristate "Parallel port IDE device support"
101 depends on PARPORT_PC
103 There are many external CD-ROM and disk devices that connect through
104 your computer's parallel port. Most of them are actually IDE devices
105 using a parallel port IDE adapter. This option enables the PARIDE
106 subsystem which contains drivers for many of these external drives.
107 Read <file:Documentation/blockdev/paride.txt> for more information.
109 If you have said Y to the "Parallel-port support" configuration
110 option, you may share a single port between your printer and other
111 parallel port devices. Answer Y to build PARIDE support into your
112 kernel, or M if you would like to build it as a loadable module. If
113 your parallel port support is in a loadable module, you must build
114 PARIDE as a module. If you built PARIDE support into your kernel,
115 you may still build the individual protocol modules and high-level
116 drivers as loadable modules. If you build this support as a module,
117 it will be called paride.
119 To use the PARIDE support, you must say Y or M here and also to at
120 least one high-level driver (e.g. "Parallel port IDE disks",
121 "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
122 to at least one protocol driver (e.g. "ATEN EH-100 protocol",
123 "MicroSolutions backpack protocol", "DataStor Commuter protocol"
126 source "drivers/block/paride/Kconfig"
128 source "drivers/block/mtip32xx/Kconfig"
130 source "drivers/block/zram/Kconfig"
132 config BLK_DEV_DAC960
133 tristate "Mylex DAC960/DAC1100 PCI RAID Controller support"
136 This driver adds support for the Mylex DAC960, AcceleRAID, and
137 eXtremeRAID PCI RAID controllers. See the file
138 <file:Documentation/blockdev/README.DAC960> for further information
141 To compile this driver as a module, choose M here: the
142 module will be called DAC960.
145 tristate "Micro Memory MM5415 Battery Backed RAM support"
148 Saying Y here will include support for the MM5415 family of
149 battery backed (Non-volatile) RAM cards.
150 <http://www.umem.com/>
152 The cards appear as block devices that can be partitioned into
153 as many as 15 partitions.
155 To compile this driver as a module, choose M here: the
156 module will be called umem.
158 The umem driver has not yet been allocated a MAJOR number, so
159 one is chosen dynamically.
162 bool "Virtual block device"
165 The User-Mode Linux port includes a driver called UBD which will let
166 you access arbitrary files on the host computer as block devices.
167 Unless you know that you do not need such virtual block devices say
170 config BLK_DEV_UBD_SYNC
171 bool "Always do synchronous disk IO for UBD"
172 depends on BLK_DEV_UBD
174 Writes to the virtual block device are not immediately written to the
175 host's disk; this may cause problems if, for example, the User-Mode
176 Linux 'Virtual Machine' uses a journalling filesystem and the host
179 Synchronous operation (i.e. always writing data to the host's disk
180 immediately) is configurable on a per-UBD basis by using a special
181 kernel command line option. Alternatively, you can say Y here to
182 turn on synchronous operation by default for all block devices.
184 If you're running a journalling file system (like reiserfs, for
185 example) in your virtual machine, you will want to say Y here. If
186 you care for the safety of the data in your virtual machine, Y is a
187 wise choice too. In all other cases (for example, if you're just
188 playing around with User-Mode Linux) you can choose N.
190 config BLK_DEV_COW_COMMON
195 tristate "Loopback device support"
197 Saying Y here will allow you to use a regular file as a block
198 device; you can then create a file system on that block device and
199 mount it just as you would mount other block devices such as hard
200 drive partitions, CD-ROM drives or floppy drives. The loop devices
201 are block special device files with major number 7 and typically
202 called /dev/loop0, /dev/loop1 etc.
204 This is useful if you want to check an ISO 9660 file system before
205 burning the CD, or if you want to use floppy images without first
206 writing them to floppy. Furthermore, some Linux distributions avoid
207 the need for a dedicated Linux partition by keeping their complete
208 root file system inside a DOS FAT file using this loop device
211 To use the loop device, you need the losetup utility, found in the
212 util-linux package, see
213 <https://www.kernel.org/pub/linux/utils/util-linux/>.
215 The loop device driver can also be used to "hide" a file system in
216 a disk partition, floppy, or regular file, either using encryption
217 (scrambling the data) or steganography (hiding the data in the low
218 bits of, say, a sound file). This is also safe if the file resides
219 on a remote file server.
221 There are several ways of encrypting disks. Some of these require
222 kernel patches. The vanilla kernel offers the cryptoloop option
223 and a Device Mapper target (which is superior, as it supports all
224 file systems). If you want to use the cryptoloop, say Y to both
225 LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12
226 or later) version of util-linux. Additionally, be aware that
227 the cryptoloop is not safe for storing journaled filesystems.
229 Note that this loop device has nothing to do with the loopback
230 device used for network connections from the machine to itself.
232 To compile this driver as a module, choose M here: the
233 module will be called loop.
235 Most users will answer N here.
237 config BLK_DEV_LOOP_MIN_COUNT
238 int "Number of loop devices to pre-create at init time"
239 depends on BLK_DEV_LOOP
242 Static number of loop devices to be unconditionally pre-created
245 This default value can be overwritten on the kernel command
246 line or with module-parameter loop.max_loop.
248 The historic default is 8. If a late 2011 version of losetup(8)
249 is used, it can be set to 0, since needed loop devices can be
250 dynamically allocated with the /dev/loop-control interface.
252 config BLK_DEV_CRYPTOLOOP
253 tristate "Cryptoloop Support (DEPRECATED)"
256 depends on BLK_DEV_LOOP
258 Say Y here if you want to be able to use the ciphers that are
259 provided by the CryptoAPI as loop transformation. This might be
260 used as hard disk encryption.
262 WARNING: This device is not safe for journaled file systems like
263 ext3 or Reiserfs. Please use the Device Mapper crypto module
264 instead, which can be configured to be on-disk compatible with the
265 cryptoloop device. cryptoloop support will be removed in Linux 5.16.
267 source "drivers/block/drbd/Kconfig"
270 tristate "Network block device support"
273 Saying Y here will allow your computer to be a client for network
274 block devices, i.e. it will be able to use block devices exported by
275 servers (mount file systems on them etc.). Communication between
276 client and server works over TCP/IP networking, but to the client
277 program this is hidden: it looks like a regular local file access to
278 a block device special file such as /dev/nd0.
280 Network block devices also allows you to run a block-device in
281 userland (making server and client physically the same computer,
282 communicating using the loopback network device).
284 Read <file:Documentation/blockdev/nbd.txt> for more information,
285 especially about where to find the server code, which runs in user
286 space and does not need special kernel support.
288 Note that this has nothing to do with the network file systems NFS
289 or Coda; you can say N here even if you intend to use NFS or Coda.
291 To compile this driver as a module, choose M here: the
292 module will be called nbd.
297 tristate "STEC S1120 Block Driver"
301 Saying Y or M here will enable support for the
302 STEC, Inc. S1120 PCIe SSD.
304 Use device /dev/skd$N amd /dev/skd$Np$M.
307 tristate "Promise SATA SX8 support"
310 Saying Y or M here will enable support for the
311 Promise SATA SX8 controllers.
313 Use devices /dev/sx8/$N and /dev/sx8/$Np$M.
316 tristate "RAM block device support"
317 select DAX if BLK_DEV_RAM_DAX
319 Saying Y here will allow you to use a portion of your RAM memory as
320 a block device, so that you can make file systems on it, read and
321 write to it and do all the other things that you can do with normal
322 block devices (such as hard drives). It is usually used to load and
323 store a copy of a minimal root file system off of a floppy into RAM
324 during the initial install of Linux.
326 Note that the kernel command line option "ramdisk=XX" is now obsolete.
327 For details, read <file:Documentation/blockdev/ramdisk.txt>.
329 To compile this driver as a module, choose M here: the
330 module will be called brd. An alias "rd" has been defined
331 for historical reasons.
333 Most normal users won't need the RAM disk functionality, and can
336 config BLK_DEV_RAM_COUNT
337 int "Default number of RAM disks"
339 depends on BLK_DEV_RAM
341 The default value is 16 RAM disks. Change this if you know what you
342 are doing. If you boot from a filesystem that needs to be extracted
343 in memory, you will need at least one RAM disk (e.g. root on cramfs).
345 config BLK_DEV_RAM_SIZE
346 int "Default RAM disk size (kbytes)"
347 depends on BLK_DEV_RAM
350 The default value is 4096 kilobytes. Only change this if you know
353 config BLK_DEV_RAM_DAX
354 bool "Support Direct Access (DAX) to RAM block devices"
355 depends on BLK_DEV_RAM && FS_DAX
358 Support filesystems using DAX to access RAM block devices. This
359 avoids double-buffering data in the page cache before copying it
360 to the block device. Answering Y will slightly enlarge the kernel,
361 and will prevent RAM block device backing store memory from being
362 allocated from highmem (only a problem for highmem systems).
365 tristate "Packet writing on CD/DVD media (DEPRECATED)"
367 select BLK_SCSI_REQUEST
369 Note: This driver is deprecated and will be removed from the
370 kernel in the near future!
372 If you have a CDROM/DVD drive that supports packet writing, say
373 Y to include support. It should work with any MMC/Mt Fuji
374 compliant ATAPI or SCSI drive, which is just about any newer
377 Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs
379 DVD-RW disks must be in restricted overwrite mode.
381 See the file <file:Documentation/cdrom/packet-writing.txt>
382 for further information on the use of this driver.
384 To compile this driver as a module, choose M here: the
385 module will be called pktcdvd.
387 config CDROM_PKTCDVD_BUFFERS
388 int "Free buffers for data gathering"
389 depends on CDROM_PKTCDVD
392 This controls the maximum number of active concurrent packets. More
393 concurrent packets can increase write performance, but also require
394 more memory. Each concurrent packet will require approximately 64Kb
395 of non-swappable kernel memory, memory which will be allocated when
396 a disc is opened for writing.
398 config CDROM_PKTCDVD_WCACHE
399 bool "Enable write caching"
400 depends on CDROM_PKTCDVD
402 If enabled, write caching will be set for the CD-R/W device. For now
403 this option is dangerous unless the CD-RW media is known good, as we
404 don't do deferred write error handling yet.
407 tristate "ATA over Ethernet support"
410 This driver provides Support for ATA over Ethernet block
411 devices like the Coraid EtherDrive (R) Storage Blade.
414 tristate "Sun Virtual Disk Client support"
417 Support for virtual disk devices as a client under Sun
420 source "drivers/s390/block/Kconfig"
423 tristate "Xilinx SystemACE support"
424 depends on 4xx || MICROBLAZE
426 Include support for the Xilinx SystemACE CompactFlash interface
428 config XEN_BLKDEV_FRONTEND
429 tristate "Xen virtual block device support"
432 select XEN_XENBUS_FRONTEND
434 This driver implements the front-end of the Xen virtual
435 block device driver. It communicates with a back-end driver
436 in another domain which drives the actual block device.
438 config XEN_BLKDEV_BACKEND
439 tristate "Xen block-device backend driver"
440 depends on XEN_BACKEND
442 The block-device backend driver allows the kernel to export its
443 block devices to other guests via a high-performance shared-memory
446 The corresponding Linux frontend driver is enabled by the
447 CONFIG_XEN_BLKDEV_FRONTEND configuration option.
449 The backend driver attaches itself to a any block device specified
450 in the XenBus configuration. There are no limits to what the block
451 device as long as it has a major and minor.
453 If you are compiling a kernel to run in a Xen block backend driver
454 domain (often this is domain 0) you should say Y here. To
455 compile this driver as a module, chose M here: the module
456 will be called xen-blkback.
460 tristate "Virtio block driver"
463 This is the virtual block driver for virtio. It can be used with
464 QEMU based VMMs (like KVM or Xen). Say Y or M.
466 config VIRTIO_BLK_SCSI
467 bool "SCSI passthrough request for the Virtio block driver"
468 depends on VIRTIO_BLK
469 select BLK_SCSI_REQUEST
471 Enable support for SCSI passthrough (e.g. the SG_IO ioctl) on
472 virtio-blk devices. This is only supported for the legacy
473 virtio protocol and not enabled by default by any hypervisor.
474 You probably want to use virtio-scsi instead.
477 tristate "Rados block device (RBD)"
478 depends on INET && BLOCK
485 Say Y here if you want include the Rados block device, which stripes
486 a block device over objects stored in the Ceph distributed object
489 More information at http://ceph.newdream.net/.
494 tristate "IBM Flash Adapter 900GB Full Height PCIe Device Driver"
498 Device driver for IBM's high speed PCIe SSD
499 storage device: Flash Adapter 900GB Full Height.
501 To compile this driver as a module, choose M here: the
502 module will be called rsxx.