summaryrefslogtreecommitdiff
path: root/drivers/nvme/target/Makefile
diff options
context:
space:
mode:
authorChristoph Hellwig <hch@lst.de>2016-06-21 19:04:21 +0300
committerJens Axboe <axboe@fb.com>2016-07-05 20:30:36 +0300
commit3a85a5de29ea779634ddfd768059e06196687aba (patch)
treeb2c055a70538069b89089b17730e3a0ce0fa2452 /drivers/nvme/target/Makefile
parenta07b4970f464f13640e28e16dad6cfa33647cc99 (diff)
downloadlinux-3a85a5de29ea779634ddfd768059e06196687aba.tar.xz
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/Makefile')
-rw-r--r--drivers/nvme/target/Makefile2
1 files changed, 2 insertions, 0 deletions
diff --git a/drivers/nvme/target/Makefile b/drivers/nvme/target/Makefile
index b4600b6f5724..e49ba60756d4 100644
--- a/drivers/nvme/target/Makefile
+++ b/drivers/nvme/target/Makefile
@@ -1,5 +1,7 @@
obj-$(CONFIG_NVME_TARGET) += nvmet.o
+obj-$(CONFIG_NVME_TARGET_LOOP) += nvme-loop.o
nvmet-y += core.o configfs.o admin-cmd.o io-cmd.o fabrics-cmd.o \
discovery.o
+nvme-loop-y += loop.o