diff options
author | Christoph Hellwig <hch@lst.de> | 2016-06-21 18:04:21 +0200 |
---|---|---|
committer | Jens Axboe <axboe@fb.com> | 2016-07-05 19:30:36 +0200 |
commit | 3a85a5de29ea779634ddfd768059e06196687aba (patch) | |
tree | b2c055a70538069b89089b17730e3a0ce0fa2452 /drivers/nvme/Kconfig | |
parent | nvmet: add a generic NVMe target (diff) | |
download | linux-3a85a5de29ea779634ddfd768059e06196687aba.tar.xz linux-3a85a5de29ea779634ddfd768059e06196687aba.zip |
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/Kconfig')
0 files changed, 0 insertions, 0 deletions