| Christoph Hellwig | a07b497 | 2016-06-21 18:04:20 +0200 | [diff] [blame] | 1 | |
| 2 | config NVME_TARGET |
| 3 | tristate "NVMe Target support" |
| 4 | depends on BLOCK |
| 5 | depends on CONFIGFS_FS |
| 6 | help |
| 7 | This enabled target side support for the NVMe protocol, that is |
| 8 | it allows the Linux kernel to implement NVMe subsystems and |
| 9 | controllers and export Linux block devices as NVMe namespaces. |
| 10 | You need to select at least one of the transports below to make this |
| 11 | functionality useful. |
| 12 | |
| 13 | To configure the NVMe target you probably want to use the nvmetcli |
| 14 | tool from http://git.infradead.org/users/hch/nvmetcli.git. |
| 15 | |
| Christoph Hellwig | 3a85a5d | 2016-06-21 18:04:21 +0200 | [diff] [blame] | 16 | config NVME_TARGET_LOOP |
| 17 | tristate "NVMe loopback device support" |
| Arnd Bergmann | 6eae8c4 | 2016-07-12 08:36:40 -0700 | [diff] [blame] | 18 | depends on NVME_TARGET |
| Christoph Hellwig | aa71987 | 2016-08-18 11:16:36 -0700 | [diff] [blame] | 19 | select NVME_CORE |
| Christoph Hellwig | 3a85a5d | 2016-06-21 18:04:21 +0200 | [diff] [blame] | 20 | select NVME_FABRICS |
| 21 | select SG_POOL |
| 22 | help |
| 23 | This enables the NVMe loopback device support, which can be useful |
| 24 | to test NVMe host and target side features. |
| 25 | |
| Christoph Hellwig | a07b497 | 2016-06-21 18:04:20 +0200 | [diff] [blame] | 26 | If unsure, say N. |
| Christoph Hellwig | 8f000ca | 2016-07-06 21:55:51 +0900 | [diff] [blame] | 27 | |
| 28 | config NVME_TARGET_RDMA |
| 29 | tristate "NVMe over Fabrics RDMA target support" |
| Arnd Bergmann | 533d1da | 2018-05-25 23:29:59 +0200 | [diff] [blame^] | 30 | depends on INFINIBAND && INFINIBAND_ADDR_TRANS |
| Arnd Bergmann | 6eae8c4 | 2016-07-12 08:36:40 -0700 | [diff] [blame] | 31 | depends on NVME_TARGET |
| Bart Van Assche | 68c6e9c | 2018-01-05 08:26:49 -0800 | [diff] [blame] | 32 | select SGL_ALLOC |
| Christoph Hellwig | 8f000ca | 2016-07-06 21:55:51 +0900 | [diff] [blame] | 33 | help |
| 34 | This enables the NVMe RDMA target support, which allows exporting NVMe |
| 35 | devices over RDMA. |
| 36 | |
| 37 | If unsure, say N. |
| James Smart | c534320 | 2016-12-02 00:28:43 -0800 | [diff] [blame] | 38 | |
| 39 | config NVME_TARGET_FC |
| 40 | tristate "NVMe over Fabrics FC target driver" |
| 41 | depends on NVME_TARGET |
| 42 | depends on HAS_DMA |
| Bart Van Assche | 4442b56 | 2018-01-05 08:26:48 -0800 | [diff] [blame] | 43 | select SGL_ALLOC |
| James Smart | c534320 | 2016-12-02 00:28:43 -0800 | [diff] [blame] | 44 | help |
| 45 | This enables the NVMe FC target support, which allows exporting NVMe |
| 46 | devices over FC. |
| 47 | |
| 48 | If unsure, say N. |
| 49 | |
| James Smart | 475d0fe | 2016-12-02 00:28:44 -0800 | [diff] [blame] | 50 | config NVME_TARGET_FCLOOP |
| 51 | tristate "NVMe over Fabrics FC Transport Loopback Test driver" |
| 52 | depends on NVME_TARGET |
| 53 | select NVME_CORE |
| 54 | select NVME_FABRICS |
| 55 | select SG_POOL |
| 56 | depends on NVME_FC |
| 57 | depends on NVME_TARGET_FC |
| 58 | help |
| 59 | This enables the NVMe FC loopback test support, which can be useful |
| 60 | to test NVMe-FC transport interfaces. |
| 61 | |
| 62 | If unsure, say N. |