]>
Commit | Line | Data |
---|---|---|
576d55d6 ML |
1 | config NVME_CORE |
2 | tristate | |
3 | ||
57dacad5 JS |
4 | config BLK_DEV_NVME |
5 | tristate "NVM Express block device" | |
11feb18f | 6 | depends on PCI && BLOCK |
576d55d6 | 7 | select NVME_CORE |
57dacad5 JS |
8 | ---help--- |
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. | |
12 | ||
13 | To compile this driver as a module, choose M here: the | |
14 | module will be called nvme. | |
44907332 CH |
15 | |
16 | config BLK_DEV_NVME_SCSI | |
17 | bool "SCSI emulation for NVMe device nodes" | |
576d55d6 | 18 | depends on NVME_CORE |
44907332 CH |
19 | ---help--- |
20 | This adds support for the SG_IO ioctl on the NVMe character | |
b31356df | 21 | and block devices nodes, as well as a translation for a small |
44907332 CH |
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 | |
21d14788 CH |
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. | |
07bfcd09 | 27 | |
12e6f749 RN |
28 | config NVME_VENDOR_EXT_GOOGLE |
29 | bool "NVMe Vendor Extension for Improved Virtualization" | |
30 | depends on BLK_DEV_NVME | |
31 | ---help--- | |
32 | Google extension to reduce the number of MMIO doorbell | |
33 | writes for the NVMe driver | |
34 | ||
07bfcd09 CH |
35 | config NVME_FABRICS |
36 | tristate | |
71102307 CH |
37 | |
38 | config NVME_RDMA | |
39 | tristate "NVM Express over Fabrics RDMA host driver" | |
bd0b841f | 40 | depends on INFINIBAND && BLOCK |
aa719874 | 41 | select NVME_CORE |
71102307 CH |
42 | select NVME_FABRICS |
43 | select SG_POOL | |
44 | help | |
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. | |
48 | ||
49 | To configure a NVMe over Fabrics controller use the nvme-cli tool | |
50 | from https://github.com/linux-nvme/nvme-cli. | |
51 | ||
52 | If unsure, say N. | |
e399441d JS |
53 | |
54 | config NVME_FC | |
55 | tristate "NVM Express over Fabrics FC host driver" | |
56 | depends on BLOCK | |
57 | depends on HAS_DMA | |
58 | select NVME_CORE | |
59 | select NVME_FABRICS | |
60 | select SG_POOL | |
61 | help | |
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. | |
65 | ||
66 | To configure a NVMe over Fabrics controller use the nvme-cli tool | |
67 | from https://github.com/linux-nvme/nvme-cli. | |
68 | ||
69 | If unsure, say N. |