| .. | .. |
|---|
| 1 | +# SPDX-License-Identifier: GPL-2.0-only |
|---|
| 1 | 2 | |
|---|
| 2 | 3 | config NVME_TARGET |
|---|
| 3 | 4 | tristate "NVMe Target support" |
|---|
| 4 | 5 | depends on BLOCK |
|---|
| 5 | 6 | depends on CONFIGFS_FS |
|---|
| 7 | + select BLK_DEV_INTEGRITY_T10 if BLK_DEV_INTEGRITY |
|---|
| 8 | + select SGL_ALLOC |
|---|
| 6 | 9 | help |
|---|
| 7 | 10 | This enabled target side support for the NVMe protocol, that is |
|---|
| 8 | 11 | it allows the Linux kernel to implement NVMe subsystems and |
|---|
| .. | .. |
|---|
| 12 | 15 | |
|---|
| 13 | 16 | To configure the NVMe target you probably want to use the nvmetcli |
|---|
| 14 | 17 | tool from http://git.infradead.org/users/hch/nvmetcli.git. |
|---|
| 18 | + |
|---|
| 19 | +config NVME_TARGET_PASSTHRU |
|---|
| 20 | + bool "NVMe Target Passthrough support" |
|---|
| 21 | + depends on NVME_TARGET |
|---|
| 22 | + depends on NVME_CORE=y || NVME_CORE=NVME_TARGET |
|---|
| 23 | + help |
|---|
| 24 | + This enables target side NVMe passthru controller support for the |
|---|
| 25 | + NVMe Over Fabrics protocol. It allows for hosts to manage and |
|---|
| 26 | + directly access an actual NVMe controller residing on the target |
|---|
| 27 | + side, incuding executing Vendor Unique Commands. |
|---|
| 28 | + |
|---|
| 29 | + If unsure, say N. |
|---|
| 15 | 30 | |
|---|
| 16 | 31 | config NVME_TARGET_LOOP |
|---|
| 17 | 32 | tristate "NVMe loopback device support" |
|---|
| .. | .. |
|---|
| 60 | 75 | to test NVMe-FC transport interfaces. |
|---|
| 61 | 76 | |
|---|
| 62 | 77 | If unsure, say N. |
|---|
| 78 | + |
|---|
| 79 | +config NVME_TARGET_TCP |
|---|
| 80 | + tristate "NVMe over Fabrics TCP target support" |
|---|
| 81 | + depends on INET |
|---|
| 82 | + depends on NVME_TARGET |
|---|
| 83 | + help |
|---|
| 84 | + This enables the NVMe TCP target support, which allows exporting NVMe |
|---|
| 85 | + devices over TCP. |
|---|
| 86 | + |
|---|
| 87 | + If unsure, say N. |
|---|