| 1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859 |
- config NVME_CORE
- tristate
- config BLK_DEV_NVME
- tristate "NVM Express block device"
- depends on PCI && BLOCK
- select NVME_CORE
- ---help---
- 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 NVME_MULTIPATH
- bool "NVMe multipath support"
- depends on NVME_CORE
- ---help---
- This option enables support for multipath access to NVMe
- subsystems. If this option is enabled only a single
- /dev/nvmeXnY device will show up for each NVMe namespaces,
- even if it is accessible through multiple controllers.
- config NVME_FABRICS
- tristate
- config NVME_RDMA
- tristate "NVM Express over Fabrics RDMA host driver"
- depends on INFINIBAND && INFINIBAND_ADDR_TRANS && BLOCK
- select NVME_CORE
- select NVME_FABRICS
- select SG_POOL
- help
- This provides support for the NVMe over Fabrics protocol using
- the RDMA (Infiniband, RoCE, iWarp) transport. This allows you
- to use remote block devices exported using the NVMe protocol set.
- To configure a NVMe over Fabrics controller use the nvme-cli tool
- from https://github.com/linux-nvme/nvme-cli.
- If unsure, say N.
- config NVME_FC
- tristate "NVM Express over Fabrics FC host driver"
- depends on BLOCK
- depends on HAS_DMA
- select NVME_CORE
- select NVME_FABRICS
- select SG_POOL
- help
- This provides support for the NVMe over Fabrics protocol using
- the FC transport. This allows you to use remote block devices
- exported using the NVMe protocol set.
- To configure a NVMe over Fabrics controller use the nvme-cli tool
- from https://github.com/linux-nvme/nvme-cli.
- If unsure, say N.
|
