Lines Matching full:block

3 # Block device driver configuration
7 	bool "Block devices"
8 	depends on BLOCK
11 	  Say Y here to get to see options for various different block device
19 source "drivers/block/null_blk/Kconfig"
20 source "drivers/block/rnull/Kconfig"
107 source "drivers/block/mtip32xx/Kconfig"
109 source "drivers/block/zram/Kconfig"
112 	bool "Virtual block device"
116           you access arbitrary files on the host computer as block devices.
117           Unless you know that you do not need such virtual block devices say
124 	  Writes to the virtual block device are not immediately written to the
132           turn on synchronous operation by default for all block devices.
147 	  Saying Y here will allow you to use a regular file as a block
148 	  device; you can then create a file system on that block device and
149 	  mount it just as you would mount other block devices such as hard
151 	  are block special device files with major number 7 and typically
194 source "drivers/block/drbd/Kconfig"
197 	tristate "Network block device support"
201 	  block devices, i.e. it will be able to use block devices exported by
205 	  a block device special file such as /dev/nd0.
207 	  Network block devices also allows you to run a block-device in
224 	tristate "RAM block device support"
227 	  a block device, so that you can make file systems on it, read and
229 	  block devices (such as hard drives). It is usually used to load and
264 	This driver provides Support for ATA over Ethernet block
274 source "drivers/s390/block/Kconfig"
277 	tristate "Xen virtual block device support"
283 	  block device driver.  It communicates with a back-end driver
284 	  in another domain which drives the actual block device.
287 	tristate "Xen block-device backend driver"
290 	  The block-device backend driver allows the kernel to export its
291 	  block devices to other guests via a high-performance shared-memory
297 	  The backend driver attaches itself to a any block device specified
298 	  in the XenBus configuration. There are no limits to what the block
301 	  If you are compiling a kernel to run in a Xen block backend driver
308 	tristate "Virtio block driver"
312 	  This is the virtual block driver for virtio.  It can be used with
316 	tristate "Rados block device (RBD)"
317 	depends on INET && BLOCK
320 	  Say Y here if you want include the Rados block device, which stripes
321 	  a block device over objects stored in the Ceph distributed object
329 	tristate "Userspace block driver (Experimental)"
332 	  io_uring based userspace block driver. Together with ublk server, ublk
354 source "drivers/block/rnbd/Kconfig"
360 	  Saying Y here will allow you to use create a zoned block device using
362 	  file systems, device mapper and applications that support zoned block