From: Chaitanya Kulkarni <[email protected]>
This patch updates KConfig file for the NVMeOF target where we add new
option so that user can selectively enable/disable passthru code.
Signed-off-by: Chaitanya Kulkarni <[email protected]>
[[email protected]: fixed some of the wording in the help message]
Signed-off-by: Logan Gunthorpe <[email protected]>
---
drivers/nvme/target/Kconfig | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/drivers/nvme/target/Kconfig b/drivers/nvme/target/Kconfig
index d7f48c0fb311..2478cb5a932d 100644
--- a/drivers/nvme/target/Kconfig
+++ b/drivers/nvme/target/Kconfig
@@ -15,6 +15,16 @@ config NVME_TARGET
To configure the NVMe target you probably want to use the nvmetcli
tool from http://git.infradead.org/users/hch/nvmetcli.git.
+config NVME_TARGET_PASSTHRU
+ bool "NVMe Target Passthrough support"
+ depends on NVME_CORE
+ depends on NVME_TARGET
+ help
+ This enables target side NVMe passthru controller support for the
+ NVMe Over Fabrics protocol. It allows for hosts to manage and
+ directly access an actual NVMe controller residing on the target
+ side, incuding executing Vendor Unique Commands.
+
config NVME_TARGET_LOOP
tristate "NVMe loopback device support"
depends on NVME_TARGET
--
2.20.1
> +config NVME_TARGET_PASSTHRU
> + bool "NVMe Target Passthrough support"
> + depends on NVME_CORE
> + depends on NVME_TARGET
> + help
> + This enables target side NVMe passthru controller support for the
> + NVMe Over Fabrics protocol. It allows for hosts to manage and
> + directly access an actual NVMe controller residing on the target
> + side, incuding executing Vendor Unique Commands.
If unsure, say N ?