Skip to content
This repository


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
tree: 9bb3c4469e
Fetching contributors…


Cannot retrieve contributors at this time

file 545 lines (448 sloc) 19.136 kb
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544
# Block device driver configuration

menuconfig BLK_DEV
bool "Block devices"
depends on BLOCK
default y
Say Y here to get to see options for various different block device
drivers. This option alone does not add any kernel code.

If you say N, all options in this submenu will be skipped and disabled;
only do this if you know what you are doing.


config BLK_DEV_FD
tristate "Normal floppy disk support"
If you want to use the floppy disk drive(s) of your PC under Linux,
say Y. Information about this driver, especially important for IBM
Thinkpad users, is contained in
That file also contains the location of the Floppy driver FAQ as
well as location of the fdutils package used to configure additional
parameters of the driver at run time.

To compile this driver as a module, choose M here: the
module will be called floppy.

tristate "Amiga floppy support"
depends on AMIGA

tristate "Atari floppy support"
depends on ATARI

tristate "Support for PowerMac floppy"
depends on PPC_PMAC && !PPC_PMAC64
If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
floppy controller, say Y here. Most commonly found in PowerMacs.

tristate "Support for SWIM Macintosh floppy"
depends on M68K && MAC
You should select this option if you want floppy support
and you don't have a II, IIfx, Q900, Q950 or AV series.

config AMIGA_Z2RAM
tristate "Amiga Zorro II ramdisk support"
depends on ZORRO
This enables support for using Chip RAM and Zorro II RAM as a
ramdisk or as a swap partition. Say Y if you want to include this
driver in the kernel.

To compile this driver as a module, choose M here: the
module will be called z2ram.

config GDROM
tristate "SEGA Dreamcast GD-ROM drive"
depends on SH_DREAMCAST
A standard SEGA Dreamcast comes with a modified CD ROM drive called a
"GD-ROM" by SEGA to signify it is capable of reading special disks
with up to 1 GB of data. This drive will also read standard CD ROM
disks. Select this option to access any disks in your GD ROM drive.
Most users will want to say "Y" here.
You can also build this as a module which will be called gdrom.

config PARIDE
tristate "Parallel port IDE device support"
depends on PARPORT_PC
There are many external CD-ROM and disk devices that connect through
your computer's parallel port. Most of them are actually IDE devices
using a parallel port IDE adapter. This option enables the PARIDE
subsystem which contains drivers for many of these external drives.
Read <file:Documentation/blockdev/paride.txt> for more information.

If you have said Y to the "Parallel-port support" configuration
option, you may share a single port between your printer and other
parallel port devices. Answer Y to build PARIDE support into your
kernel, or M if you would like to build it as a loadable module. If
your parallel port support is in a loadable module, you must build
PARIDE as a module. If you built PARIDE support into your kernel,
you may still build the individual protocol modules and high-level
drivers as loadable modules. If you build this support as a module,
it will be called paride.

To use the PARIDE support, you must say Y or M here and also to at
least one high-level driver (e.g. "Parallel port IDE disks",
"Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
to at least one protocol driver (e.g. "ATEN EH-100 protocol",
"MicroSolutions backpack protocol", "DataStor Commuter protocol"

source "drivers/block/paride/Kconfig"

source "drivers/block/mtip32xx/Kconfig"

config BLK_CPQ_DA
tristate "Compaq SMART2 support"
depends on PCI && VIRT_TO_BUS
This is the driver for Compaq Smart Array controllers. Everyone
using these boards should say Y here. See the file
<file:Documentation/blockdev/cpqarray.txt> for the current list of
boards supported by this driver, and for further information on the
use of this driver.

tristate "Compaq Smart Array 5xxx support"
depends on PCI
This is the driver for Compaq Smart Array 5xxx controllers.
Everyone using these boards should say Y here.
See <file:Documentation/blockdev/cciss.txt> for the current list of
boards supported by this driver, and for further information
on the use of this driver.

bool "SCSI tape drive support for Smart Array 5xxx"
depends on BLK_CPQ_CISS_DA && PROC_FS
depends on SCSI=y || SCSI=BLK_CPQ_CISS_DA
When enabled (Y), this option allows SCSI tape drives and SCSI medium
changers (tape robots) to be accessed via a Compaq 5xxx array
controller. (See <file:Documentation/blockdev/cciss.txt> for more details.)

"SCSI support" and "SCSI tape support" must also be enabled for this
option to work.

When this option is disabled (N), the SCSI portion of the driver
is not compiled.

config BLK_DEV_DAC960
tristate "Mylex DAC960/DAC1100 PCI RAID Controller support"
depends on PCI
This driver adds support for the Mylex DAC960, AcceleRAID, and
eXtremeRAID PCI RAID controllers. See the file
<file:Documentation/blockdev/README.DAC960> for further information
about this driver.

To compile this driver as a module, choose M here: the
module will be called DAC960.

tristate "Micro Memory MM5415 Battery Backed RAM support"
depends on PCI
Saying Y here will include support for the MM5415 family of
battery backed (Non-volatile) RAM cards.

The cards appear as block devices that can be partitioned into
as many as 15 partitions.

To compile this driver as a module, choose M here: the
module will be called umem.

The umem driver has not yet been allocated a MAJOR number, so
one is chosen dynamically.

config BLK_DEV_UBD
bool "Virtual block device"
depends on UML
          The User-Mode Linux port includes a driver called UBD which will let
          you access arbitrary files on the host computer as block devices.
          Unless you know that you do not need such virtual block devices say
          Y here.

bool "Always do synchronous disk IO for UBD"
depends on BLK_DEV_UBD
Writes to the virtual block device are not immediately written to the
host's disk; this may cause problems if, for example, the User-Mode
Linux 'Virtual Machine' uses a journalling filesystem and the host
computer crashes.

          Synchronous operation (i.e. always writing data to the host's disk
          immediately) is configurable on a per-UBD basis by using a special
          kernel command line option. Alternatively, you can say Y here to
          turn on synchronous operation by default for all block devices.

          If you're running a journalling file system (like reiserfs, for
          example) in your virtual machine, you will want to say Y here. If
          you care for the safety of the data in your virtual machine, Y is a
          wise choice too. In all other cases (for example, if you're just
          playing around with User-Mode Linux) you can choose N.

default BLK_DEV_UBD

tristate "Loopback device support"
Saying Y here will allow you to use a regular file as a block
device; you can then create a file system on that block device and
mount it just as you would mount other block devices such as hard
drive partitions, CD-ROM drives or floppy drives. The loop devices
are block special device files with major number 7 and typically
called /dev/loop0, /dev/loop1 etc.

This is useful if you want to check an ISO 9660 file system before
burning the CD, or if you want to use floppy images without first
writing them to floppy. Furthermore, some Linux distributions avoid
the need for a dedicated Linux partition by keeping their complete
root file system inside a DOS FAT file using this loop device

To use the loop device, you need the losetup utility, found in the
util-linux package, see

The loop device driver can also be used to "hide" a file system in
a disk partition, floppy, or regular file, either using encryption
(scrambling the data) or steganography (hiding the data in the low
bits of, say, a sound file). This is also safe if the file resides
on a remote file server.

There are several ways of encrypting disks. Some of these require
kernel patches. The vanilla kernel offers the cryptoloop option
and a Device Mapper target (which is superior, as it supports all
file systems). If you want to use the cryptoloop, say Y to both
LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12
or later) version of util-linux. Additionally, be aware that
the cryptoloop is not safe for storing journaled filesystems.

Note that this loop device has nothing to do with the loopback
device used for network connections from the machine to itself.

To compile this driver as a module, choose M here: the
module will be called loop.

Most users will answer N here.

int "Number of loop devices to pre-create at init time"
depends on BLK_DEV_LOOP
default 8
Static number of loop devices to be unconditionally pre-created
at init time.

This default value can be overwritten on the kernel command
line or with module-parameter loop.max_loop.

The historic default is 8. If a late 2011 version of losetup(8)
is used, it can be set to 0, since needed loop devices can be
dynamically allocated with the /dev/loop-control interface.

tristate "Cryptoloop Support"
select CRYPTO
depends on BLK_DEV_LOOP
Say Y here if you want to be able to use the ciphers that are
provided by the CryptoAPI as loop transformation. This might be
used as hard disk encryption.

WARNING: This device is not safe for journaled file systems like
ext3 or Reiserfs. Please use the Device Mapper crypto module
instead, which can be configured to be on-disk compatible with the
cryptoloop device.

source "drivers/block/drbd/Kconfig"

config BLK_DEV_NBD
tristate "Network block device support"
depends on NET
Saying Y here will allow your computer to be a client for network
block devices, i.e. it will be able to use block devices exported by
servers (mount file systems on them etc.). Communication between
client and server works over TCP/IP networking, but to the client
program this is hidden: it looks like a regular local file access to
a block device special file such as /dev/nd0.

Network block devices also allows you to run a block-device in
userland (making server and client physically the same computer,
communicating using the loopback network device).

Read <file:Documentation/blockdev/nbd.txt> for more information,
especially about where to find the server code, which runs in user
space and does not need special kernel support.

Note that this has nothing to do with the network file systems NFS
or Coda; you can say N here even if you intend to use NFS or Coda.

To compile this driver as a module, choose M here: the
module will be called nbd.

If unsure, say N.

tristate "NVM Express block device"
depends on PCI
The NVM Express driver is for solid state drives directly
connected to the PCI or PCI Express bus. If you know you
don't have one of these, it is safe to answer N.

To compile this driver as a module, choose M here: the
module will be called nvme.

config BLK_DEV_OSD
tristate "OSD object-as-blkdev support"
depends on SCSI_OSD_ULD
Saying Y or M here will allow the exporting of a single SCSI
OSD (object-based storage) object as a Linux block device.

For example, if you create a 2G object on an OSD device,
you can then use this module to present that 2G object as
a Linux block device.

To compile this driver as a module, choose M here: the
module will be called osdblk.

If unsure, say N.

config BLK_DEV_SX8
tristate "Promise SATA SX8 support"
depends on PCI
Saying Y or M here will enable support for the
Promise SATA SX8 controllers.

Use devices /dev/sx8/$N and /dev/sx8/$Np$M.

config BLK_DEV_RAM
tristate "RAM block device support"
Saying Y here will allow you to use a portion of your RAM memory as
a block device, so that you can make file systems on it, read and
write to it and do all the other things that you can do with normal
block devices (such as hard drives). It is usually used to load and
store a copy of a minimal root file system off of a floppy into RAM
during the initial install of Linux.

Note that the kernel command line option "ramdisk=XX" is now obsolete.
For details, read <file:Documentation/blockdev/ramdisk.txt>.

To compile this driver as a module, choose M here: the
module will be called rd.

Most normal users won't need the RAM disk functionality, and can
thus say N here.

int "Default number of RAM disks"
default "16"
depends on BLK_DEV_RAM
The default value is 16 RAM disks. Change this if you know what you
are doing. If you boot from a filesystem that needs to be extracted
in memory, you will need at least one RAM disk (e.g. root on cramfs).

int "Default RAM disk size (kbytes)"
depends on BLK_DEV_RAM
default "4096"
The default value is 4096 kilobytes. Only change this if you know
what you are doing.

config BLK_DEV_XIP
bool "Support XIP filesystems on RAM block device"
depends on BLK_DEV_RAM
default n
Support XIP filesystems (such as ext2 with XIP support on) on
top of block ram device. This will slightly enlarge the kernel, and
will prevent RAM block device backing store memory from being
allocated from highmem (only a problem for highmem systems).

tristate "Packet writing on CD/DVD media"
depends on !UML
If you have a CDROM/DVD drive that supports packet writing, say
Y to include support. It should work with any MMC/Mt Fuji
compliant ATAPI or SCSI drive, which is just about any newer
DVD/CD writer.

Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs
is possible.
DVD-RW disks must be in restricted overwrite mode.

See the file <file:Documentation/cdrom/packet-writing.txt>
for further information on the use of this driver.

To compile this driver as a module, choose M here: the
module will be called pktcdvd.

int "Free buffers for data gathering"
depends on CDROM_PKTCDVD
default "8"
This controls the maximum number of active concurrent packets. More
concurrent packets can increase write performance, but also require
more memory. Each concurrent packet will require approximately 64Kb
of non-swappable kernel memory, memory which will be allocated when
a disc is opened for writing.

bool "Enable write caching"
depends on CDROM_PKTCDVD
If enabled, write caching will be set for the CD-R/W device. For now
this option is dangerous unless the CD-RW media is known good, as we
don't do deferred write error handling yet.

tristate "ATA over Ethernet support"
depends on NET
This driver provides Support for ATA over Ethernet block
devices like the Coraid EtherDrive (R) Storage Blade.

config MG_DISK
tristate "mGine mflash, gflash support"
depends on ARM && GPIOLIB
mGine mFlash(gFlash) block device driver

config MG_DISK_RES
int "Size of reserved area before MBR"
depends on MG_DISK
default 0
Define size of reserved area that usually used for boot. Unit is KB.
All of the block device operation will be taken this value as start
1024 => 1 MB

config SUNVDC
tristate "Sun Virtual Disk Client support"
depends on SUN_LDOMS
Support for virtual disk devices as a client under Sun
Logical Domains.

source "drivers/s390/block/Kconfig"

tristate "Xilinx SystemACE support"
depends on 4xx || MICROBLAZE
Include support for the Xilinx SystemACE CompactFlash interface

tristate "Xen virtual block device support"
depends on XEN
default y
This driver implements the front-end of the Xen virtual
block device driver. It communicates with a back-end driver
in another domain which drives the actual block device.

tristate "Xen block-device backend driver"
depends on XEN_BACKEND
The block-device backend driver allows the kernel to export its
block devices to other guests via a high-performance shared-memory

The corresponding Linux frontend driver is enabled by the
CONFIG_XEN_BLKDEV_FRONTEND configuration option.

The backend driver attaches itself to a any block device specified
in the XenBus configuration. There are no limits to what the block
device as long as it has a major and minor.

If you are compiling a kernel to run in a Xen block backend driver
domain (often this is domain 0) you should say Y here. To
compile this driver as a module, chose M here: the module
will be called xen-blkback.

tristate "Virtio block driver"
depends on VIRTIO
This is the virtual block driver for virtio. It can be used with
          lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.

config BLK_DEV_HD
bool "Very old hard disk (MFM/RLL/IDE) driver"
depends on HAVE_IDE
depends on !ARM || ARCH_RPC || ARCH_SHARK || BROKEN
This is a very old hard disk driver that lacks the enhanced
functionality of the newer ones.

It is required for systems with ancient MFM/RLL/ESDI drives.

If unsure, say N.

config BLK_DEV_RBD
tristate "Rados block device (RBD)"
depends on INET && BLOCK
select CEPH_LIB
select LIBCRC32C
select CRYPTO
default n
Say Y here if you want include the Rados block device, which stripes
a block device over objects stored in the Ceph distributed object

More information at

If unsure, say N.

tristate "IBM FlashSystem 70/80 PCIe SSD Device Driver"
depends on PCI
Device driver for IBM's high speed PCIe SSD
storage devices: FlashSystem-70 and FlashSystem-80.

To compile this driver as a module, choose M here: the
module will be called rsxx.

endif # BLK_DEV
Something went wrong with that request. Please try again.