kernel/linux.git/drivers/nvme/target/loop.c, branch v4.8.16Linux kernel stable tree (mirror)https://git.radix-linux.su/kernel/linux.git/atom?h=v4.8.162016-08-18T06:58:06+00:00nvme-loop: set sqsize to 0-based value, per spec2016-08-18T06:58:06+00:00Jay Freyenseejames_p_freyensee@linux.intel.com2016-08-17T22:00:28+00:00urn:sha1:eadb7cf44105ae8250f0d638dc880c3ed511c4e2
Signed-off-by: Jay Freyensee <james_p_freyensee@linux.intel.com>
Signed-off-by: Sagi Grimberg <sagi@grimberg.me>
nvme-loop: Remove duplicate call to nvme_remove_namespaces2016-08-03T13:25:19+00:00Sagi Grimbergsagi@grimberg.me2016-07-24T06:32:08+00:00urn:sha1:a159c64d936eb0d1da29d8ad384183d8984899c9
nvme_uninit_ctrl already does that for us. Note that we
reordered nvme_loop_shutdown_ctrl with nvme_uninit_ctrl
but its safe because we want controller uninit to happen
before we shutdown the transport resources.
Signed-off-by: Sagi Grimberg <sagi@grimberg.me>
Reviewed-by: Christoph Hellwig <hch@lst.de>
nvme-loop: add a NVMe loopback host driver2016-07-05T17:30:36+00:00Christoph Hellwighch@lst.de2016-06-21T16:04:21+00:00urn:sha1:3a85a5de29ea779634ddfd768059e06196687aba
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>