^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1) # SPDX-License-Identifier: GPL-2.0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2) #
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 3) # Block device driver configuration
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 4) #
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 5)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 6) menuconfig BLK_DEV
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 7) bool "Block devices"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 8) depends on BLOCK
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 9) default y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 10) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 11) Say Y here to get to see options for various different block device
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 12) drivers. This option alone does not add any kernel code.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 13)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 14) If you say N, all options in this submenu will be skipped and disabled;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 15) only do this if you know what you are doing.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 16)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 17) if BLK_DEV
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 18)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 19) config BLK_DEV_NULL_BLK
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 20) tristate "Null test block driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 21) select CONFIGFS_FS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 22)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 23) config BLK_DEV_NULL_BLK_FAULT_INJECTION
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 24) bool "Support fault injection for Null test block driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 25) depends on BLK_DEV_NULL_BLK && FAULT_INJECTION
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 26)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 27) config BLK_DEV_FD
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 28) tristate "Normal floppy disk support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 29) depends on ARCH_MAY_HAVE_PC_FDC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 30) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 31) If you want to use the floppy disk drive(s) of your PC under Linux,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 32) say Y. Information about this driver, especially important for IBM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 33) Thinkpad users, is contained in
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 34) <file:Documentation/admin-guide/blockdev/floppy.rst>.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 35) That file also contains the location of the Floppy driver FAQ as
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 36) well as location of the fdutils package used to configure additional
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 37) parameters of the driver at run time.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 38)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 39) To compile this driver as a module, choose M here: the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 40) module will be called floppy.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 41)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 42) config AMIGA_FLOPPY
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 43) tristate "Amiga floppy support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 44) depends on AMIGA
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 45)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 46) config ATARI_FLOPPY
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 47) tristate "Atari floppy support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 48) depends on ATARI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 49)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 50) config MAC_FLOPPY
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 51) tristate "Support for PowerMac floppy"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 52) depends on PPC_PMAC && !PPC_PMAC64
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 53) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 54) If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 55) floppy controller, say Y here. Most commonly found in PowerMacs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 56)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 57) config BLK_DEV_SWIM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 58) tristate "Support for SWIM Macintosh floppy"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 59) depends on M68K && MAC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 60) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 61) You should select this option if you want floppy support
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 62) and you don't have a II, IIfx, Q900, Q950 or AV series.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 63)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 64) config AMIGA_Z2RAM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 65) tristate "Amiga Zorro II ramdisk support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 66) depends on ZORRO
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 67) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 68) This enables support for using Chip RAM and Zorro II RAM as a
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 69) ramdisk or as a swap partition. Say Y if you want to include this
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 70) driver in the kernel.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 71)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 72) To compile this driver as a module, choose M here: the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 73) module will be called z2ram.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 74)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 75) config CDROM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 76) tristate
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 77) select BLK_SCSI_REQUEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 78)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 79) config GDROM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 80) tristate "SEGA Dreamcast GD-ROM drive"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 81) depends on SH_DREAMCAST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 82) select CDROM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 83) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 84) A standard SEGA Dreamcast comes with a modified CD ROM drive called a
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 85) "GD-ROM" by SEGA to signify it is capable of reading special disks
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 86) with up to 1 GB of data. This drive will also read standard CD ROM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 87) disks. Select this option to access any disks in your GD ROM drive.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 88) Most users will want to say "Y" here.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 89) You can also build this as a module which will be called gdrom.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 90)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 91) config PARIDE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 92) tristate "Parallel port IDE device support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 93) depends on PARPORT_PC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 94) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 95) There are many external CD-ROM and disk devices that connect through
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 96) your computer's parallel port. Most of them are actually IDE devices
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 97) using a parallel port IDE adapter. This option enables the PARIDE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 98) subsystem which contains drivers for many of these external drives.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 99) Read <file:Documentation/admin-guide/blockdev/paride.rst> for more information.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 100)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 101) If you have said Y to the "Parallel-port support" configuration
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 102) option, you may share a single port between your printer and other
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 103) parallel port devices. Answer Y to build PARIDE support into your
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 104) kernel, or M if you would like to build it as a loadable module. If
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 105) your parallel port support is in a loadable module, you must build
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 106) PARIDE as a module. If you built PARIDE support into your kernel,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 107) you may still build the individual protocol modules and high-level
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 108) drivers as loadable modules. If you build this support as a module,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 109) it will be called paride.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 110)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 111) To use the PARIDE support, you must say Y or M here and also to at
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 112) least one high-level driver (e.g. "Parallel port IDE disks",
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 113) "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 114) to at least one protocol driver (e.g. "ATEN EH-100 protocol",
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 115) "MicroSolutions backpack protocol", "DataStor Commuter protocol"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 116) etc.).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 117)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 118) source "drivers/block/paride/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 119)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 120) source "drivers/block/mtip32xx/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 121)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 122) source "drivers/block/zram/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 123)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 124) config BLK_DEV_UMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 125) tristate "Micro Memory MM5415 Battery Backed RAM support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 126) depends on PCI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 127) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 128) Saying Y here will include support for the MM5415 family of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 129) battery backed (Non-volatile) RAM cards.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 130) <http://www.umem.com/>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 131)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 132) The cards appear as block devices that can be partitioned into
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 133) as many as 15 partitions.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 134)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 135) To compile this driver as a module, choose M here: the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 136) module will be called umem.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 137)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 138) The umem driver has not yet been allocated a MAJOR number, so
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 139) one is chosen dynamically.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 140)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 141) config BLK_DEV_UBD
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 142) bool "Virtual block device"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 143) depends on UML
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 144) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 145) The User-Mode Linux port includes a driver called UBD which will let
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 146) you access arbitrary files on the host computer as block devices.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 147) Unless you know that you do not need such virtual block devices say
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 148) Y here.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 149)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 150) config BLK_DEV_UBD_SYNC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 151) bool "Always do synchronous disk IO for UBD"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 152) depends on BLK_DEV_UBD
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 153) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 154) Writes to the virtual block device are not immediately written to the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 155) host's disk; this may cause problems if, for example, the User-Mode
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 156) Linux 'Virtual Machine' uses a journalling filesystem and the host
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 157) computer crashes.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 158)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 159) Synchronous operation (i.e. always writing data to the host's disk
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 160) immediately) is configurable on a per-UBD basis by using a special
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 161) kernel command line option. Alternatively, you can say Y here to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 162) turn on synchronous operation by default for all block devices.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 163)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 164) If you're running a journalling file system (like reiserfs, for
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 165) example) in your virtual machine, you will want to say Y here. If
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 166) you care for the safety of the data in your virtual machine, Y is a
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 167) wise choice too. In all other cases (for example, if you're just
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 168) playing around with User-Mode Linux) you can choose N.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 169)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 170) config BLK_DEV_COW_COMMON
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 171) bool
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 172) default BLK_DEV_UBD
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 173)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 174) config BLK_DEV_LOOP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 175) tristate "Loopback device support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 176) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 177) Saying Y here will allow you to use a regular file as a block
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 178) device; you can then create a file system on that block device and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 179) mount it just as you would mount other block devices such as hard
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 180) drive partitions, CD-ROM drives or floppy drives. The loop devices
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 181) are block special device files with major number 7 and typically
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 182) called /dev/loop0, /dev/loop1 etc.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 183)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 184) This is useful if you want to check an ISO 9660 file system before
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 185) burning the CD, or if you want to use floppy images without first
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 186) writing them to floppy. Furthermore, some Linux distributions avoid
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 187) the need for a dedicated Linux partition by keeping their complete
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 188) root file system inside a DOS FAT file using this loop device
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 189) driver.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 190)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 191) To use the loop device, you need the losetup utility, found in the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 192) util-linux package, see
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 193) <https://www.kernel.org/pub/linux/utils/util-linux/>.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 194)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 195) The loop device driver can also be used to "hide" a file system in
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 196) a disk partition, floppy, or regular file, either using encryption
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 197) (scrambling the data) or steganography (hiding the data in the low
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 198) bits of, say, a sound file). This is also safe if the file resides
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 199) on a remote file server.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 200)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 201) There are several ways of encrypting disks. Some of these require
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 202) kernel patches. The vanilla kernel offers the cryptoloop option
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 203) and a Device Mapper target (which is superior, as it supports all
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 204) file systems). If you want to use the cryptoloop, say Y to both
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 205) LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 206) or later) version of util-linux. Additionally, be aware that
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 207) the cryptoloop is not safe for storing journaled filesystems.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 208)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 209) Note that this loop device has nothing to do with the loopback
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 210) device used for network connections from the machine to itself.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 211)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 212) To compile this driver as a module, choose M here: the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 213) module will be called loop.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 214)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 215) Most users will answer N here.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 216)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 217) config BLK_DEV_LOOP_MIN_COUNT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 218) int "Number of loop devices to pre-create at init time"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 219) depends on BLK_DEV_LOOP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 220) default 8
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 221) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 222) Static number of loop devices to be unconditionally pre-created
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 223) at init time.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 224)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 225) This default value can be overwritten on the kernel command
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 226) line or with module-parameter loop.max_loop.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 227)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 228) The historic default is 8. If a late 2011 version of losetup(8)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 229) is used, it can be set to 0, since needed loop devices can be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 230) dynamically allocated with the /dev/loop-control interface.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 231)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 232) config BLK_DEV_CRYPTOLOOP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 233) tristate "Cryptoloop Support (DEPRECATED)"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 234) select CRYPTO
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 235) select CRYPTO_CBC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 236) depends on BLK_DEV_LOOP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 237) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 238) Say Y here if you want to be able to use the ciphers that are
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 239) provided by the CryptoAPI as loop transformation. This might be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 240) used as hard disk encryption.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 241)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 242) WARNING: This device is not safe for journaled file systems like
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 243) ext3 or Reiserfs. Please use the Device Mapper crypto module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 244) instead, which can be configured to be on-disk compatible with the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 245) cryptoloop device. cryptoloop support will be removed in Linux 5.16.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 246)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 247) source "drivers/block/drbd/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 248)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 249) config BLK_DEV_NBD
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 250) tristate "Network block device support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 251) depends on NET
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 252) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 253) Saying Y here will allow your computer to be a client for network
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 254) block devices, i.e. it will be able to use block devices exported by
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 255) servers (mount file systems on them etc.). Communication between
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 256) client and server works over TCP/IP networking, but to the client
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 257) program this is hidden: it looks like a regular local file access to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 258) a block device special file such as /dev/nd0.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 259)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 260) Network block devices also allows you to run a block-device in
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 261) userland (making server and client physically the same computer,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 262) communicating using the loopback network device).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 263)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 264) Read <file:Documentation/admin-guide/blockdev/nbd.rst> for more information,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 265) especially about where to find the server code, which runs in user
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 266) space and does not need special kernel support.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 267)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 268) Note that this has nothing to do with the network file systems NFS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 269) or Coda; you can say N here even if you intend to use NFS or Coda.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 270)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 271) To compile this driver as a module, choose M here: the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 272) module will be called nbd.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 273)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 274) If unsure, say N.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 275)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 276) config BLK_DEV_SKD
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 277) tristate "STEC S1120 Block Driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 278) depends on PCI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 279) depends on 64BIT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 280) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 281) Saying Y or M here will enable support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 282) STEC, Inc. S1120 PCIe SSD.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 283)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 284) Use device /dev/skd$N amd /dev/skd$Np$M.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 285)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 286) config BLK_DEV_SX8
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 287) tristate "Promise SATA SX8 support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 288) depends on PCI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 289) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 290) Saying Y or M here will enable support for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 291) Promise SATA SX8 controllers.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 292)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 293) Use devices /dev/sx8/$N and /dev/sx8/$Np$M.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 294)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 295) config BLK_DEV_RAM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 296) tristate "RAM block device support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 297) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 298) Saying Y here will allow you to use a portion of your RAM memory as
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 299) a block device, so that you can make file systems on it, read and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 300) write to it and do all the other things that you can do with normal
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 301) block devices (such as hard drives). It is usually used to load and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 302) store a copy of a minimal root file system off of a floppy into RAM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 303) during the initial install of Linux.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 304)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 305) Note that the kernel command line option "ramdisk=XX" is now obsolete.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 306) For details, read <file:Documentation/admin-guide/blockdev/ramdisk.rst>.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 307)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 308) To compile this driver as a module, choose M here: the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 309) module will be called brd. An alias "rd" has been defined
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 310) for historical reasons.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 311)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 312) Most normal users won't need the RAM disk functionality, and can
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 313) thus say N here.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 314)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 315) config BLK_DEV_RAM_COUNT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 316) int "Default number of RAM disks"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 317) default "16"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 318) depends on BLK_DEV_RAM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 319) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 320) The default value is 16 RAM disks. Change this if you know what you
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 321) are doing. If you boot from a filesystem that needs to be extracted
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 322) in memory, you will need at least one RAM disk (e.g. root on cramfs).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 323)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 324) config BLK_DEV_RAM_SIZE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 325) int "Default RAM disk size (kbytes)"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 326) depends on BLK_DEV_RAM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 327) default "4096"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 328) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 329) The default value is 4096 kilobytes. Only change this if you know
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 330) what you are doing.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 331)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 332) config CDROM_PKTCDVD
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 333) tristate "Packet writing on CD/DVD media (DEPRECATED)"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 334) depends on !UML
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 335) select CDROM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 336) select BLK_SCSI_REQUEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 337) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 338) Note: This driver is deprecated and will be removed from the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 339) kernel in the near future!
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 340)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 341) If you have a CDROM/DVD drive that supports packet writing, say
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 342) Y to include support. It should work with any MMC/Mt Fuji
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 343) compliant ATAPI or SCSI drive, which is just about any newer
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 344) DVD/CD writer.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 345)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 346) Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 347) is possible.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 348) DVD-RW disks must be in restricted overwrite mode.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 349)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 350) See the file <file:Documentation/cdrom/packet-writing.rst>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 351) for further information on the use of this driver.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 352)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 353) To compile this driver as a module, choose M here: the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 354) module will be called pktcdvd.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 355)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 356) config CDROM_PKTCDVD_BUFFERS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 357) int "Free buffers for data gathering"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 358) depends on CDROM_PKTCDVD
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 359) default "8"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 360) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 361) This controls the maximum number of active concurrent packets. More
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 362) concurrent packets can increase write performance, but also require
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 363) more memory. Each concurrent packet will require approximately 64Kb
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 364) of non-swappable kernel memory, memory which will be allocated when
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 365) a disc is opened for writing.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 366)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 367) config CDROM_PKTCDVD_WCACHE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 368) bool "Enable write caching"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 369) depends on CDROM_PKTCDVD
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 370) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 371) If enabled, write caching will be set for the CD-R/W device. For now
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 372) this option is dangerous unless the CD-RW media is known good, as we
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 373) don't do deferred write error handling yet.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 374)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 375) config ATA_OVER_ETH
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 376) tristate "ATA over Ethernet support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 377) depends on NET
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 378) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 379) This driver provides Support for ATA over Ethernet block
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 380) devices like the Coraid EtherDrive (R) Storage Blade.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 381)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 382) config SUNVDC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 383) tristate "Sun Virtual Disk Client support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 384) depends on SUN_LDOMS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 385) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 386) Support for virtual disk devices as a client under Sun
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 387) Logical Domains.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 388)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 389) source "drivers/s390/block/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 390)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 391) config XILINX_SYSACE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 392) tristate "Xilinx SystemACE support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 393) depends on 4xx || MICROBLAZE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 394) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 395) Include support for the Xilinx SystemACE CompactFlash interface
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 396)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 397) config XEN_BLKDEV_FRONTEND
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 398) tristate "Xen virtual block device support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 399) depends on XEN
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 400) default y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 401) select XEN_XENBUS_FRONTEND
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 402) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 403) This driver implements the front-end of the Xen virtual
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 404) block device driver. It communicates with a back-end driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 405) in another domain which drives the actual block device.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 406)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 407) config XEN_BLKDEV_BACKEND
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 408) tristate "Xen block-device backend driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 409) depends on XEN_BACKEND
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 410) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 411) The block-device backend driver allows the kernel to export its
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 412) block devices to other guests via a high-performance shared-memory
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 413) interface.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 414)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 415) The corresponding Linux frontend driver is enabled by the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 416) CONFIG_XEN_BLKDEV_FRONTEND configuration option.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 417)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 418) The backend driver attaches itself to a any block device specified
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 419) in the XenBus configuration. There are no limits to what the block
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 420) device as long as it has a major and minor.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 421)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 422) If you are compiling a kernel to run in a Xen block backend driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 423) domain (often this is domain 0) you should say Y here. To
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 424) compile this driver as a module, chose M here: the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 425) will be called xen-blkback.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 426)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 427)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 428) config VIRTIO_BLK
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 429) tristate "Virtio block driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 430) depends on VIRTIO
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 431) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 432) This is the virtual block driver for virtio. It can be used with
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 433) QEMU based VMMs (like KVM or Xen). Say Y or M.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 434)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 435) config BLK_DEV_RBD
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 436) tristate "Rados block device (RBD)"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 437) depends on INET && BLOCK
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 438) select CEPH_LIB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 439) select LIBCRC32C
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 440) select CRYPTO_AES
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 441) select CRYPTO
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 442) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 443) Say Y here if you want include the Rados block device, which stripes
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 444) a block device over objects stored in the Ceph distributed object
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 445) store.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 446)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 447) More information at http://ceph.newdream.net/.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 448)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 449) If unsure, say N.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 450)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 451) config BLK_DEV_RSXX
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 452) tristate "IBM Flash Adapter 900GB Full Height PCIe Device Driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 453) depends on PCI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 454) select CRC32
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 455) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 456) Device driver for IBM's high speed PCIe SSD
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 457) storage device: Flash Adapter 900GB Full Height.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 458)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 459) To compile this driver as a module, choose M here: the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 460) module will be called rsxx.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 461)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 462) source "drivers/block/rnbd/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 463)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 464) endif # BLK_DEV
Orange Pi5 kernel
Deprecated Linux kernel 5.10.110 for OrangePi 5/5B/5+ boards
3 Commits
0 Branches
0 Tags