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.
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 && !HIGHMEM
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 bool "N64 cart support"
71 depends on MACH_NINTENDO64
73 Support for the N64 cart.
79 tristate "SEGA Dreamcast GD-ROM drive"
80 depends on SH_DREAMCAST
83 A standard SEGA Dreamcast comes with a modified CD ROM drive called a
84 "GD-ROM" by SEGA to signify it is capable of reading special disks
85 with up to 1 GB of data. This drive will also read standard CD ROM
86 disks. Select this option to access any disks in your GD ROM drive.
87 Most users will want to say "Y" here.
88 You can also build this as a module which will be called gdrom.
91 tristate "Parallel port IDE device support"
94 There are many external CD-ROM and disk devices that connect through
95 your computer's parallel port. Most of them are actually IDE devices
96 using a parallel port IDE adapter. This option enables the PARIDE
97 subsystem which contains drivers for many of these external drives.
98 Read <file:Documentation/admin-guide/blockdev/paride.rst> for more information.
100 If you have said Y to the "Parallel-port support" configuration
101 option, you may share a single port between your printer and other
102 parallel port devices. Answer Y to build PARIDE support into your
103 kernel, or M if you would like to build it as a loadable module. If
104 your parallel port support is in a loadable module, you must build
105 PARIDE as a module. If you built PARIDE support into your kernel,
106 you may still build the individual protocol modules and high-level
107 drivers as loadable modules. If you build this support as a module,
108 it will be called paride.
110 To use the PARIDE support, you must say Y or M here and also to at
111 least one high-level driver (e.g. "Parallel port IDE disks",
112 "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
113 to at least one protocol driver (e.g. "ATEN EH-100 protocol",
114 "MicroSolutions backpack protocol", "DataStor Commuter protocol"
117 source "drivers/block/paride/Kconfig"
119 source "drivers/block/mtip32xx/Kconfig"
121 source "drivers/block/zram/Kconfig"
124 bool "Virtual block device"
127 The User-Mode Linux port includes a driver called UBD which will let
128 you access arbitrary files on the host computer as block devices.
129 Unless you know that you do not need such virtual block devices say
132 config BLK_DEV_UBD_SYNC
133 bool "Always do synchronous disk IO for UBD"
134 depends on BLK_DEV_UBD
136 Writes to the virtual block device are not immediately written to the
137 host's disk; this may cause problems if, for example, the User-Mode
138 Linux 'Virtual Machine' uses a journalling filesystem and the host
141 Synchronous operation (i.e. always writing data to the host's disk
142 immediately) is configurable on a per-UBD basis by using a special
143 kernel command line option. Alternatively, you can say Y here to
144 turn on synchronous operation by default for all block devices.
146 If you're running a journalling file system (like reiserfs, for
147 example) in your virtual machine, you will want to say Y here. If
148 you care for the safety of the data in your virtual machine, Y is a
149 wise choice too. In all other cases (for example, if you're just
150 playing around with User-Mode Linux) you can choose N.
152 config BLK_DEV_COW_COMMON
157 tristate "Loopback device support"
159 Saying Y here will allow you to use a regular file as a block
160 device; you can then create a file system on that block device and
161 mount it just as you would mount other block devices such as hard
162 drive partitions, CD-ROM drives or floppy drives. The loop devices
163 are block special device files with major number 7 and typically
164 called /dev/loop0, /dev/loop1 etc.
166 This is useful if you want to check an ISO 9660 file system before
167 burning the CD, or if you want to use floppy images without first
168 writing them to floppy. Furthermore, some Linux distributions avoid
169 the need for a dedicated Linux partition by keeping their complete
170 root file system inside a DOS FAT file using this loop device
173 To use the loop device, you need the losetup utility, found in the
174 util-linux package, see
175 <https://www.kernel.org/pub/linux/utils/util-linux/>.
177 The loop device driver can also be used to "hide" a file system in
178 a disk partition, floppy, or regular file, either using encryption
179 (scrambling the data) or steganography (hiding the data in the low
180 bits of, say, a sound file). This is also safe if the file resides
181 on a remote file server.
183 There are several ways of encrypting disks. Some of these require
184 kernel patches. The vanilla kernel offers the cryptoloop option
185 and a Device Mapper target (which is superior, as it supports all
186 file systems). If you want to use the cryptoloop, say Y to both
187 LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12
188 or later) version of util-linux. Additionally, be aware that
189 the cryptoloop is not safe for storing journaled filesystems.
191 Note that this loop device has nothing to do with the loopback
192 device used for network connections from the machine to itself.
194 To compile this driver as a module, choose M here: the
195 module will be called loop.
197 Most users will answer N here.
199 config BLK_DEV_LOOP_MIN_COUNT
200 int "Number of loop devices to pre-create at init time"
201 depends on BLK_DEV_LOOP
204 Static number of loop devices to be unconditionally pre-created
207 This default value can be overwritten on the kernel command
208 line or with module-parameter loop.max_loop.
210 The historic default is 8. If a late 2011 version of losetup(8)
211 is used, it can be set to 0, since needed loop devices can be
212 dynamically allocated with the /dev/loop-control interface.
214 config BLK_DEV_CRYPTOLOOP
215 tristate "Cryptoloop Support (DEPRECATED)"
218 depends on BLK_DEV_LOOP
220 Say Y here if you want to be able to use the ciphers that are
221 provided by the CryptoAPI as loop transformation. This might be
222 used as hard disk encryption.
224 WARNING: This device is not safe for journaled file systems like
225 ext3 or Reiserfs. Please use the Device Mapper crypto module
226 instead, which can be configured to be on-disk compatible with the
227 cryptoloop device. cryptoloop support will be removed in Linux 5.16.
229 source "drivers/block/drbd/Kconfig"
232 tristate "Network block device support"
235 Saying Y here will allow your computer to be a client for network
236 block devices, i.e. it will be able to use block devices exported by
237 servers (mount file systems on them etc.). Communication between
238 client and server works over TCP/IP networking, but to the client
239 program this is hidden: it looks like a regular local file access to
240 a block device special file such as /dev/nd0.
242 Network block devices also allows you to run a block-device in
243 userland (making server and client physically the same computer,
244 communicating using the loopback network device).
246 Read <file:Documentation/admin-guide/blockdev/nbd.rst> for more information,
247 especially about where to find the server code, which runs in user
248 space and does not need special kernel support.
250 Note that this has nothing to do with the network file systems NFS
251 or Coda; you can say N here even if you intend to use NFS or Coda.
253 To compile this driver as a module, choose M here: the
254 module will be called nbd.
259 tristate "Promise SATA SX8 support"
262 Saying Y or M here will enable support for the
263 Promise SATA SX8 controllers.
265 Use devices /dev/sx8/$N and /dev/sx8/$Np$M.
268 tristate "RAM block device support"
270 Saying Y here will allow you to use a portion of your RAM memory as
271 a block device, so that you can make file systems on it, read and
272 write to it and do all the other things that you can do with normal
273 block devices (such as hard drives). It is usually used to load and
274 store a copy of a minimal root file system off of a floppy into RAM
275 during the initial install of Linux.
277 Note that the kernel command line option "ramdisk=XX" is now obsolete.
278 For details, read <file:Documentation/admin-guide/blockdev/ramdisk.rst>.
280 To compile this driver as a module, choose M here: the
281 module will be called brd. An alias "rd" has been defined
282 for historical reasons.
284 Most normal users won't need the RAM disk functionality, and can
287 config BLK_DEV_RAM_COUNT
288 int "Default number of RAM disks"
290 depends on BLK_DEV_RAM
292 The default value is 16 RAM disks. Change this if you know what you
293 are doing. If you boot from a filesystem that needs to be extracted
294 in memory, you will need at least one RAM disk (e.g. root on cramfs).
296 config BLK_DEV_RAM_SIZE
297 int "Default RAM disk size (kbytes)"
298 depends on BLK_DEV_RAM
301 The default value is 4096 kilobytes. Only change this if you know
305 tristate "Packet writing on CD/DVD media (DEPRECATED)"
310 Note: This driver is deprecated and will be removed from the
311 kernel in the near future!
313 If you have a CDROM/DVD drive that supports packet writing, say
314 Y to include support. It should work with any MMC/Mt Fuji
315 compliant ATAPI or SCSI drive, which is just about any newer
318 Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs
320 DVD-RW disks must be in restricted overwrite mode.
322 See the file <file:Documentation/cdrom/packet-writing.rst>
323 for further information on the use of this driver.
325 To compile this driver as a module, choose M here: the
326 module will be called pktcdvd.
328 config CDROM_PKTCDVD_BUFFERS
329 int "Free buffers for data gathering"
330 depends on CDROM_PKTCDVD
333 This controls the maximum number of active concurrent packets. More
334 concurrent packets can increase write performance, but also require
335 more memory. Each concurrent packet will require approximately 64Kb
336 of non-swappable kernel memory, memory which will be allocated when
337 a disc is opened for writing.
339 config CDROM_PKTCDVD_WCACHE
340 bool "Enable write caching"
341 depends on CDROM_PKTCDVD
343 If enabled, write caching will be set for the CD-R/W device. For now
344 this option is dangerous unless the CD-RW media is known good, as we
345 don't do deferred write error handling yet.
348 tristate "ATA over Ethernet support"
351 This driver provides Support for ATA over Ethernet block
352 devices like the Coraid EtherDrive (R) Storage Blade.
355 tristate "Sun Virtual Disk Client support"
358 Support for virtual disk devices as a client under Sun
361 source "drivers/s390/block/Kconfig"
363 config XEN_BLKDEV_FRONTEND
364 tristate "Xen virtual block device support"
367 select XEN_XENBUS_FRONTEND
369 This driver implements the front-end of the Xen virtual
370 block device driver. It communicates with a back-end driver
371 in another domain which drives the actual block device.
373 config XEN_BLKDEV_BACKEND
374 tristate "Xen block-device backend driver"
375 depends on XEN_BACKEND
377 The block-device backend driver allows the kernel to export its
378 block devices to other guests via a high-performance shared-memory
381 The corresponding Linux frontend driver is enabled by the
382 CONFIG_XEN_BLKDEV_FRONTEND configuration option.
384 The backend driver attaches itself to a any block device specified
385 in the XenBus configuration. There are no limits to what the block
386 device as long as it has a major and minor.
388 If you are compiling a kernel to run in a Xen block backend driver
389 domain (often this is domain 0) you should say Y here. To
390 compile this driver as a module, chose M here: the module
391 will be called xen-blkback.
395 tristate "Virtio block driver"
398 This is the virtual block driver for virtio. It can be used with
399 QEMU based VMMs (like KVM or Xen). Say Y or M.
402 tristate "Rados block device (RBD)"
403 depends on INET && BLOCK
409 Say Y here if you want include the Rados block device, which stripes
410 a block device over objects stored in the Ceph distributed object
413 More information at http://ceph.newdream.net/.
418 tristate "IBM Flash Adapter 900GB Full Height PCIe Device Driver"
422 Device driver for IBM's high speed PCIe SSD
423 storage device: Flash Adapter 900GB Full Height.
425 To compile this driver as a module, choose M here: the
426 module will be called rsxx.
428 source "drivers/block/rnbd/Kconfig"