From: keith.busch@intel.com (Keith Busch)
Subject: [RFC PATCH] nvmet: Back namespace with files
Date: Wed, 8 Mar 2017 17:15:28 -0500 [thread overview]
Message-ID: <20170308221527.GA1885@localhost.localdomain> (raw)
In-Reply-To: <20170308213519.GA32009@lst.de>
On Wed, Mar 08, 2017@10:35:19PM +0100, Christoph Hellwig wrote:
> Wrong kind of interface - this needs to use vfs_iter_read/write
> of type ITER_BVEC.
Gotchya, that's what I was locking for. Thanks for the pointer.
> And before merging anything I'd really like to see how this is
> an improvement over simply using the loop device.
This is a step toward getting namespace management. It's easy to create
namespaces if they're files.
next prev parent reply other threads:[~2017-03-08 22:15 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 [this message]
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
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=20170308221527.GA1885@localhost.localdomain \
--to=keith.busch@intel.com \
/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).