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 source "drivers/block/null_blk/Kconfig"
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/admin-guide/blockdev/floppy.rst>.
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.
36 config BLK_DEV_FD_RAWCMD
37 bool "Support for raw floppy disk commands (DEPRECATED)"
40 If you want to use actual physical floppies and expect to do
41 special low-level hardware accesses to them (access and use
42 non-standard formats, for example), then enable this.
44 Note that the code enabled by this option is rarely used and
45 might be unstable or insecure, and distros should not enable it.
47 Note: FDRAWCMD is deprecated and will be removed from the kernel
53 tristate "Amiga floppy support"
57 tristate "Atari floppy support"
61 tristate "Support for PowerMac floppy"
62 depends on PPC_PMAC && !PPC_PMAC64
64 If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
65 floppy controller, say Y here. Most commonly found in PowerMacs.
68 tristate "Support for SWIM Macintosh floppy"
69 depends on M68K && MAC
71 You should select this option if you want floppy support
72 and you don't have a II, IIfx, Q900, Q950 or AV series.
75 tristate "Amiga Zorro II ramdisk support"
78 This enables support for using Chip RAM and Zorro II RAM as a
79 ramdisk or as a swap partition. Say Y if you want to include this
82 To compile this driver as a module, choose M here: the
83 module will be called z2ram.
87 select BLK_SCSI_REQUEST
90 tristate "SEGA Dreamcast GD-ROM drive"
91 depends on SH_DREAMCAST
94 A standard SEGA Dreamcast comes with a modified CD ROM drive called a
95 "GD-ROM" by SEGA to signify it is capable of reading special disks
96 with up to 1 GB of data. This drive will also read standard CD ROM
97 disks. Select this option to access any disks in your GD ROM drive.
98 Most users will want to say "Y" here.
99 You can also build this as a module which will be called gdrom.
102 tristate "Parallel port IDE device support"
103 depends on PARPORT_PC
105 There are many external CD-ROM and disk devices that connect through
106 your computer's parallel port. Most of them are actually IDE devices
107 using a parallel port IDE adapter. This option enables the PARIDE
108 subsystem which contains drivers for many of these external drives.
109 Read <file:Documentation/admin-guide/blockdev/paride.rst> for more information.
111 If you have said Y to the "Parallel-port support" configuration
112 option, you may share a single port between your printer and other
113 parallel port devices. Answer Y to build PARIDE support into your
114 kernel, or M if you would like to build it as a loadable module. If
115 your parallel port support is in a loadable module, you must build
116 PARIDE as a module. If you built PARIDE support into your kernel,
117 you may still build the individual protocol modules and high-level
118 drivers as loadable modules. If you build this support as a module,
119 it will be called paride.
121 To use the PARIDE support, you must say Y or M here and also to at
122 least one high-level driver (e.g. "Parallel port IDE disks",
123 "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
124 to at least one protocol driver (e.g. "ATEN EH-100 protocol",
125 "MicroSolutions backpack protocol", "DataStor Commuter protocol"
128 source "drivers/block/paride/Kconfig"
130 source "drivers/block/mtip32xx/Kconfig"
132 source "drivers/block/zram/Kconfig"
135 tristate "Micro Memory MM5415 Battery Backed RAM support"
138 Saying Y here will include support for the MM5415 family of
139 battery backed (Non-volatile) RAM cards.
140 <http://www.umem.com/>
142 The cards appear as block devices that can be partitioned into
143 as many as 15 partitions.
145 To compile this driver as a module, choose M here: the
146 module will be called umem.
148 The umem driver has not yet been allocated a MAJOR number, so
149 one is chosen dynamically.
152 bool "Virtual block device"
155 The User-Mode Linux port includes a driver called UBD which will let
156 you access arbitrary files on the host computer as block devices.
157 Unless you know that you do not need such virtual block devices say
160 config BLK_DEV_UBD_SYNC
161 bool "Always do synchronous disk IO for UBD"
162 depends on BLK_DEV_UBD
164 Writes to the virtual block device are not immediately written to the
165 host's disk; this may cause problems if, for example, the User-Mode
166 Linux 'Virtual Machine' uses a journalling filesystem and the host
169 Synchronous operation (i.e. always writing data to the host's disk
170 immediately) is configurable on a per-UBD basis by using a special
171 kernel command line option. Alternatively, you can say Y here to
172 turn on synchronous operation by default for all block devices.
174 If you're running a journalling file system (like reiserfs, for
175 example) in your virtual machine, you will want to say Y here. If
176 you care for the safety of the data in your virtual machine, Y is a
177 wise choice too. In all other cases (for example, if you're just
178 playing around with User-Mode Linux) you can choose N.
180 config BLK_DEV_COW_COMMON
185 tristate "Loopback device support"
187 Saying Y here will allow you to use a regular file as a block
188 device; you can then create a file system on that block device and
189 mount it just as you would mount other block devices such as hard
190 drive partitions, CD-ROM drives or floppy drives. The loop devices
191 are block special device files with major number 7 and typically
192 called /dev/loop0, /dev/loop1 etc.
194 This is useful if you want to check an ISO 9660 file system before
195 burning the CD, or if you want to use floppy images without first
196 writing them to floppy. Furthermore, some Linux distributions avoid
197 the need for a dedicated Linux partition by keeping their complete
198 root file system inside a DOS FAT file using this loop device
201 To use the loop device, you need the losetup utility, found in the
202 util-linux package, see
203 <https://www.kernel.org/pub/linux/utils/util-linux/>.
205 The loop device driver can also be used to "hide" a file system in
206 a disk partition, floppy, or regular file, either using encryption
207 (scrambling the data) or steganography (hiding the data in the low
208 bits of, say, a sound file). This is also safe if the file resides
209 on a remote file server.
211 There are several ways of encrypting disks. Some of these require
212 kernel patches. The vanilla kernel offers the cryptoloop option
213 and a Device Mapper target (which is superior, as it supports all
214 file systems). If you want to use the cryptoloop, say Y to both
215 LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12
216 or later) version of util-linux. Additionally, be aware that
217 the cryptoloop is not safe for storing journaled filesystems.
219 Note that this loop device has nothing to do with the loopback
220 device used for network connections from the machine to itself.
222 To compile this driver as a module, choose M here: the
223 module will be called loop.
225 Most users will answer N here.
227 config BLK_DEV_LOOP_MIN_COUNT
228 int "Number of loop devices to pre-create at init time"
229 depends on BLK_DEV_LOOP
232 Static number of loop devices to be unconditionally pre-created
235 This default value can be overwritten on the kernel command
236 line or with module-parameter loop.max_loop.
238 The historic default is 8. If a late 2011 version of losetup(8)
239 is used, it can be set to 0, since needed loop devices can be
240 dynamically allocated with the /dev/loop-control interface.
242 config BLK_DEV_CRYPTOLOOP
243 tristate "Cryptoloop Support (DEPRECATED)"
246 depends on BLK_DEV_LOOP
248 Say Y here if you want to be able to use the ciphers that are
249 provided by the CryptoAPI as loop transformation. This might be
250 used as hard disk encryption.
252 WARNING: This device is not safe for journaled file systems like
253 ext3 or Reiserfs. Please use the Device Mapper crypto module
254 instead, which can be configured to be on-disk compatible with the
255 cryptoloop device. cryptoloop support will be removed in Linux 5.16.
257 source "drivers/block/drbd/Kconfig"
260 tristate "Network block device support"
263 Saying Y here will allow your computer to be a client for network
264 block devices, i.e. it will be able to use block devices exported by
265 servers (mount file systems on them etc.). Communication between
266 client and server works over TCP/IP networking, but to the client
267 program this is hidden: it looks like a regular local file access to
268 a block device special file such as /dev/nd0.
270 Network block devices also allows you to run a block-device in
271 userland (making server and client physically the same computer,
272 communicating using the loopback network device).
274 Read <file:Documentation/admin-guide/blockdev/nbd.rst> for more information,
275 especially about where to find the server code, which runs in user
276 space and does not need special kernel support.
278 Note that this has nothing to do with the network file systems NFS
279 or Coda; you can say N here even if you intend to use NFS or Coda.
281 To compile this driver as a module, choose M here: the
282 module will be called nbd.
287 tristate "STEC S1120 Block Driver"
291 Saying Y or M here will enable support for the
292 STEC, Inc. S1120 PCIe SSD.
294 Use device /dev/skd$N amd /dev/skd$Np$M.
297 tristate "RAM block device support"
299 Saying Y here will allow you to use a portion of your RAM memory as
300 a block device, so that you can make file systems on it, read and
301 write to it and do all the other things that you can do with normal
302 block devices (such as hard drives). It is usually used to load and
303 store a copy of a minimal root file system off of a floppy into RAM
304 during the initial install of Linux.
306 Note that the kernel command line option "ramdisk=XX" is now obsolete.
307 For details, read <file:Documentation/admin-guide/blockdev/ramdisk.rst>.
309 To compile this driver as a module, choose M here: the
310 module will be called brd. An alias "rd" has been defined
311 for historical reasons.
313 Most normal users won't need the RAM disk functionality, and can
316 config BLK_DEV_RAM_COUNT
317 int "Default number of RAM disks"
319 depends on BLK_DEV_RAM
321 The default value is 16 RAM disks. Change this if you know what you
322 are doing. If you boot from a filesystem that needs to be extracted
323 in memory, you will need at least one RAM disk (e.g. root on cramfs).
325 config BLK_DEV_RAM_SIZE
326 int "Default RAM disk size (kbytes)"
327 depends on BLK_DEV_RAM
330 The default value is 4096 kilobytes. Only change this if you know
334 tristate "Packet writing on CD/DVD media (DEPRECATED)"
337 select BLK_SCSI_REQUEST
339 Note: This driver is deprecated and will be removed from the
340 kernel in the near future!
342 If you have a CDROM/DVD drive that supports packet writing, say
343 Y to include support. It should work with any MMC/Mt Fuji
344 compliant ATAPI or SCSI drive, which is just about any newer
347 Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs
349 DVD-RW disks must be in restricted overwrite mode.
351 See the file <file:Documentation/cdrom/packet-writing.rst>
352 for further information on the use of this driver.
354 To compile this driver as a module, choose M here: the
355 module will be called pktcdvd.
357 config CDROM_PKTCDVD_BUFFERS
358 int "Free buffers for data gathering"
359 depends on CDROM_PKTCDVD
362 This controls the maximum number of active concurrent packets. More
363 concurrent packets can increase write performance, but also require
364 more memory. Each concurrent packet will require approximately 64Kb
365 of non-swappable kernel memory, memory which will be allocated when
366 a disc is opened for writing.
368 config CDROM_PKTCDVD_WCACHE
369 bool "Enable write caching"
370 depends on CDROM_PKTCDVD
372 If enabled, write caching will be set for the CD-R/W device. For now
373 this option is dangerous unless the CD-RW media is known good, as we
374 don't do deferred write error handling yet.
377 tristate "ATA over Ethernet support"
380 This driver provides Support for ATA over Ethernet block
381 devices like the Coraid EtherDrive (R) Storage Blade.
384 tristate "Sun Virtual Disk Client support"
387 Support for virtual disk devices as a client under Sun
390 source "drivers/s390/block/Kconfig"
393 tristate "Xilinx SystemACE support"
394 depends on 4xx || MICROBLAZE
396 Include support for the Xilinx SystemACE CompactFlash interface
398 config XEN_BLKDEV_FRONTEND
399 tristate "Xen virtual block device support"
402 select XEN_XENBUS_FRONTEND
404 This driver implements the front-end of the Xen virtual
405 block device driver. It communicates with a back-end driver
406 in another domain which drives the actual block device.
408 config XEN_BLKDEV_BACKEND
409 tristate "Xen block-device backend driver"
410 depends on XEN_BACKEND
412 The block-device backend driver allows the kernel to export its
413 block devices to other guests via a high-performance shared-memory
416 The corresponding Linux frontend driver is enabled by the
417 CONFIG_XEN_BLKDEV_FRONTEND configuration option.
419 The backend driver attaches itself to a any block device specified
420 in the XenBus configuration. There are no limits to what the block
421 device as long as it has a major and minor.
423 If you are compiling a kernel to run in a Xen block backend driver
424 domain (often this is domain 0) you should say Y here. To
425 compile this driver as a module, chose M here: the module
426 will be called xen-blkback.
430 tristate "Virtio block driver"
433 This is the virtual block driver for virtio. It can be used with
434 QEMU based VMMs (like KVM or Xen). Say Y or M.
437 tristate "Rados block device (RBD)"
438 depends on INET && BLOCK
444 Say Y here if you want include the Rados block device, which stripes
445 a block device over objects stored in the Ceph distributed object
448 More information at http://ceph.newdream.net/.
453 tristate "IBM Flash Adapter 900GB Full Height PCIe Device Driver"
457 Device driver for IBM's high speed PCIe SSD
458 storage device: Flash Adapter 900GB Full Height.
460 To compile this driver as a module, choose M here: the
461 module will be called rsxx.
463 source "drivers/block/rnbd/Kconfig"