From: james_p_freyensee@linux.intel.com (J Freyensee)
Subject: [RFC PATCH] nvmet: Back namespace with files
Date: Mon, 13 Mar 2017 11:00:01 -0700 [thread overview]
Message-ID: <1489428001.4237.0.camel@linux.intel.com> (raw)
In-Reply-To: <20170313163338.GA3324@lst.de>
On Mon, 2017-03-13@17:33 +0100, Christoph Hellwig wrote:
> On Mon, Mar 13, 2017@12:11:28PM -0400, Keith Busch wrote:
> >
> > Yes, the RFC was light on details, and I'm probably getting ahead of
> > myself with the file-as-a-namespaces suggestion.
>
> No, it's a good idea.??The big question is what we win with explicit
> support in nvmet over just using the loop device.??I actually hacked
> up support earlier and it didn't show any performance advantage.
> That being said we now have the ITER_BVEC type and proper support
> for in-kernel aio, so the code might become simple enough to just take
> it.
If it's easier to setup and maintain and use that could suffice for a lack of
performance advantage.
>
> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2017-03-13 18:00 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 [this message]
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=1489428001.4237.0.camel@linux.intel.com \
--to=james_p_freyensee@linux.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).