5 tristate "NVM Express block device"
6 depends on PCI && BLOCK
9 The NVM Express driver is for solid state drives directly
10 connected to the PCI or PCI Express bus. If you know you
11 don't have one of these, it is safe to answer N.
13 To compile this driver as a module, choose M here: the
14 module will be called nvme.
16 config BLK_DEV_NVME_SCSI
17 bool "SCSI emulation for NVMe device nodes"
20 This adds support for the SG_IO ioctl on the NVMe character
21 and block devices nodes, as well as a translation for a small
22 number of selected SCSI commands to NVMe commands to the NVMe
23 driver. If you don't know what this means you probably want
24 to say N here, unless you run a distro that abuses the SCSI
25 emulation to provide stable device names for mount by id, like
26 some OpenSuSE and SLES versions.
28 config NVME_VENDOR_EXT_GOOGLE
29 bool "NVMe Vendor Extension for Improved Virtualization"
30 depends on BLK_DEV_NVME
32 Google extension to reduce the number of MMIO doorbell
33 writes for the NVMe driver
39 tristate "NVM Express over Fabrics RDMA host driver"
40 depends on INFINIBAND && BLOCK
45 This provides support for the NVMe over Fabrics protocol using
46 the RDMA (Infiniband, RoCE, iWarp) transport. This allows you
47 to use remote block devices exported using the NVMe protocol set.
49 To configure a NVMe over Fabrics controller use the nvme-cli tool
50 from https://github.com/linux-nvme/nvme-cli.
55 tristate "NVM Express over Fabrics FC host driver"
62 This provides support for the NVMe over Fabrics protocol using
63 the FC transport. This allows you to use remote block devices
64 exported using the NVMe protocol set.
66 To configure a NVMe over Fabrics controller use the nvme-cli tool
67 from https://github.com/linux-nvme/nvme-cli.