Navigation: Linux Kernel Driver DataBase - web LKDDB: Main index - B index

CONFIG_BLK_DEV_NBD: Network block device support

General informations

The Linux kernel configuration item CONFIG_BLK_DEV_NBD has multiple definitions:

Network block device support found in arch/ia64/Kconfig

The configuration item CONFIG_BLK_DEV_NBD:

Help text

(none)

Network block device support found in arch/sparc/Kconfig

The configuration item CONFIG_BLK_DEV_NBD:

Help text

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 Documentation/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.

Network block device support found in arch/sparc64/Kconfig

The configuration item CONFIG_BLK_DEV_NBD:

Help text

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 Documentation/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.

Network block device support found in arch/um/Kconfig_block

The configuration item CONFIG_BLK_DEV_NBD:

Help text

(none)

Network block device support found in drivers/block/Kconfig

The configuration item CONFIG_BLK_DEV_NBD:

Help text

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 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.

Hardware

LKDDb

Raw data from LKDDb:

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

Automatic links from Google (and ads)

Custom Search

Popular queries:

Navigation: Linux Kernel Driver DataBase - web LKDDB: main index - B index

Automatically generated (in year 2016) with gen-web-lkddb.py in lkddb-sources.