Custom Search
Navigation: Linux Kernel Driver DataBase - web LKDDB: Main index - B index
The Linux kernel configuration item CONFIG_BLK_DEV_NBD has multiple definitions:
drivers/block/KconfigThe configuration item CONFIG_BLK_DEV_NBD:
CONFIG_NETnbd, nbd, nbd, nbd, nbd, nbdSaying 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/admin-guide/blockdev/nbd.rst 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.
arch/um/Kconfig_blockThe configuration item CONFIG_BLK_DEV_NBD:
CONFIG_NETnbd, nbd, nbd, nbd, nbd, nbd(none)
arch/ia64/KconfigThe configuration item CONFIG_BLK_DEV_NBD:
CONFIG_NETnbd, nbd, nbd, nbd, nbd, nbd(none)
arch/sparc64/KconfigThe configuration item CONFIG_BLK_DEV_NBD:
CONFIG_NETnbd, nbd, nbd, nbd, nbd, nbdSaying 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.
arch/sparc/KconfigThe configuration item CONFIG_BLK_DEV_NBD:
CONFIG_NETnbd, nbd, nbd, nbd, nbd, nbdSaying 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.
drivers/s390/KconfigThe configuration item CONFIG_BLK_DEV_NBD:
CONFIG_NETnbd, nbd, nbd, nbd, nbd, nbdSaying 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.
If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read Documentation/modules.txt. The module will be called nbd.
If unsure, say N.
Raw data from LKDDb:
lkddb module nbd CONFIG_BLK_DEV_NBD : arch/ia64/Kconfig : "Network block device support" # in 2.5.45–2.5.75, 2.6.0–2.6.4lkddb module nbd CONFIG_BLK_DEV_NBD : arch/sparc/Kconfig : "Network block device support" # in 2.5.45–2.5.75, 2.6.0lkddb module nbd CONFIG_BLK_DEV_NBD : arch/sparc64/Kconfig : "Network block device support" # in 2.5.45–2.5.75, 2.6.0lkddb module nbd CONFIG_BLK_DEV_NBD : arch/um/Kconfig_block : "Network block device support" # in 2.5.45–2.5.75, 2.6.0–2.6.10lkddb module nbd CONFIG_BLK_DEV_NBD : drivers/block/Kconfig : "Network block device support" # in 2.5.45–2.5.75, 2.6.0–2.6.39, 3.0–3.19, 4.0–4.20, 5.0–5.19, 6.0–6.12, 6.13-rc+HEADlkddb module nbd CONFIG_BLK_DEV_NBD : drivers/s390/Kconfig : "Network block device support" # in 2.5.45–2.5.75This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).
The data is retrived from:
Popular queries:
Navigation: Linux Kernel Driver DataBase - web LKDDB: main index - B index
Automatically generated (in year 2024). See also LKDDb sources on GitLab