Lines Matching refs:block

10 	  Say Y here to get to see options for various different block device
19 	tristate "Null test block driver"
107 source "drivers/block/paride/Kconfig"
109 source "drivers/block/mtip32xx/Kconfig"
111 source "drivers/block/zram/Kconfig"
169 	  The cards appear as block devices that can be partitioned into
179 	bool "Virtual block device"
183           you access arbitrary files on the host computer as block devices.
184           Unless you know that you do not need such virtual block devices say
191 	  Writes to the virtual block device are not immediately written to the
199           turn on synchronous operation by default for all block devices.
214 	  Saying Y here will allow you to use a regular file as a block
215 	  device; you can then create a file system on that block device and
216 	  mount it just as you would mount other block devices such as hard
218 	  are block special device files with major number 7 and typically
284 source "drivers/block/drbd/Kconfig"
287 	tristate "Network block device support"
291 	  block devices, i.e. it will be able to use block devices exported by
295 	  a block device special file such as /dev/nd0.
297 	  Network block devices also allows you to run a block-device in
328 	  OSD (object-based storage) object as a Linux block device.
332 	  a Linux block device.
349 	tristate "RAM block device support"
352 	  a block device, so that you can make file systems on it, read and
354 	  block devices (such as hard drives). It is usually used to load and
386 	bool "Support Direct Access (DAX) to RAM block devices"
390 	  Support filesystems using DAX to access RAM block devices.  This
392 	  to the block device.  Answering Y will slightly enlarge the kernel,
393 	  and will prevent RAM block device backing store memory from being
438 	This driver provides Support for ATA over Ethernet block
445 	  mGine mFlash(gFlash) block device driver
453 	  All of the block device operation will be taken this value as start
465 source "drivers/s390/block/Kconfig"
474 	tristate "Xen virtual block device support"
480 	  block device driver.  It communicates with a back-end driver
481 	  in another domain which drives the actual block device.
484 	tristate "Xen block-device backend driver"
487 	  The block-device backend driver allows the kernel to export its
488 	  block devices to other guests via a high-performance shared-memory
494 	  The backend driver attaches itself to a any block device specified
495 	  in the XenBus configuration. There are no limits to what the block
498 	  If you are compiling a kernel to run in a Xen block backend driver
505 	tristate "Virtio block driver"
508 	  This is the virtual block driver for virtio.  It can be used with
524 	tristate "Rados block device (RBD)"
532 	  Say Y here if you want include the Rados block device, which stripes
533 	  a block device over objects stored in the Ceph distributed object