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