From: sagi@grimberg.me (Sagi Grimberg)
Subject: [RFC PATCH] nvmet: Back namespace with files
Date: Thu, 9 Mar 2017 01:24:11 +0200 [thread overview]
Message-ID: <a067f769-166a-a444-32e3-ff488dce748a@grimberg.me> (raw)
In-Reply-To: <1489008937-31043-1-git-send-email-keith.busch@intel.com>
Keith,
> This RFC allows NVMeOF targets to be backed by files. Prior to this,
> only block device files were supported, but this patch will let you use
> any file, and continue working on block files if requested.
I don't think this is the way to go. I really don't.
> Backing with files has more flexibility on what a namespace can be,
> and it isn't difficult from here to add NVMe target support for caching,
> provisioning, namespace management, and all the features Linux filesystems
> provide.
As Christoph said, you need a *very* compelling justification why loop
doesn't give you everything you need.
> I only ported the loop target. The fc and rdma targets are a little more
> work, so this looked like a good stopping point to guage interest.
RDMA and FC is where sgls are actually important as they need dma
mapping, which means that the kvec handling is something that needs to
be pushed into the backend handling in io-cmd.c
prev parent reply other threads:[~2017-03-08 23:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 21:35 [RFC PATCH] nvmet: Back namespace with files Keith Busch
2017-03-08 21:35 ` Christoph Hellwig
2017-03-08 22:15 ` Keith Busch
2017-03-08 22:20 ` Christoph Hellwig
2017-03-09 17:41 ` Keith Busch
2017-03-09 17:39 ` Christoph Hellwig
2017-03-13 8:32 ` Sagi Grimberg
2017-03-13 16:11 ` Keith Busch
2017-03-13 16:07 ` Hannes Reinecke
2017-03-13 16:33 ` Christoph Hellwig
2017-03-13 18:00 ` J Freyensee
2017-03-08 23:24 ` Sagi Grimberg [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a067f769-166a-a444-32e3-ff488dce748a@grimberg.me \
--to=sagi@grimberg.me \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).