diff options
| author | Christoph Hellwig <hch@lst.de> | 2016-06-21 18:04:21 +0200 |
|---|---|---|
| committer | Jens Axboe <axboe@fb.com> | 2016-07-05 11:30:36 -0600 |
| commit | 3a85a5de29ea779634ddfd768059e06196687aba (patch) | |
| tree | b2c055a70538069b89089b17730e3a0ce0fa2452 /drivers/nvme/target/Kconfig | |
| parent | a07b4970f464f13640e28e16dad6cfa33647cc99 (diff) | |
nvme-loop: add a NVMe loopback host driver
This patch implements adds nvme-loop which allows to access local devices
exported as NVMe over Fabrics namespaces. This module can be useful for
easy evaluation, testing and also feature experimentation.
To createa nvme-loop device you need to configure the NVMe target to
export a loop port (see the nvmetcli documentaton for that) and then
connect to it using
nvme connect-all -t loop
which requires the very latest nvme-cli version with Fabrics support.
Signed-off-by: Jay Freyensee <james.p.freyensee@intel.com>
Signed-off-by: Ming Lin <ming.l@ssi.samsung.com>
Signed-off-by: Sagi Grimberg <sagi@grimberg.me>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Steve Wise <swise@opengridcomputing.com>
Signed-off-by: Jens Axboe <axboe@fb.com>
Diffstat (limited to 'drivers/nvme/target/Kconfig')
| -rw-r--r-- | drivers/nvme/target/Kconfig | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/drivers/nvme/target/Kconfig b/drivers/nvme/target/Kconfig index acf0c070e50d..b77ce4350695 100644 --- a/drivers/nvme/target/Kconfig +++ b/drivers/nvme/target/Kconfig @@ -13,4 +13,14 @@ 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_LOOP + tristate "NVMe loopback device support" + depends on BLK_DEV_NVME + select NVME_TARGET + select NVME_FABRICS + select SG_POOL + help + This enables the NVMe loopback device support, which can be useful + to test NVMe host and target side features. + If unsure, say N. |