linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Sushil <sushil32@gmail.com>
To: Keith Busch <kbusch@kernel.org>
Cc: linux-nvme@lists.infradead.org
Subject: Re: NVM Sets supported on Linux?
Date: Wed, 20 Nov 2019 23:33:11 +0530	[thread overview]
Message-ID: <CAOoKxP8XWhuF7ROKsTHmUpsaUvwCJS0ZH7xOXJGUKQvqUOrU+Q@mail.gmail.com> (raw)
In-Reply-To: <20191120152935.GA9426@redsun51.ssa.fujisawa.hgst.com>

Hi Keith,
Thanks for reply.

Basically, currently  I want to create NVM Sets on an NVMe disk and
export these NVM sets as LVM volumes to VM instances using Openstack.
Later on try things like Endurance, PLM etc. with these NVM sets.
We don't have any physical NVMe controller with NVM sets though.
So I was thinking whether I can use the 'nvmet' Linux target driver to
create kind of logical/virtual  NVM sets
and therefore whether target has/will have support for NVM sets. Its
like how namespaces are created on-the-fly
in Openstack during volume attachment using the volume path -
/dev/vg1/lvol1 for ex. - and the Nova compute node
then nvme connects to these newly created volume specific namespaces
and attaches them to the VM instances.

So I am thinking instead of volume path, I create NVM sets and
corresponding namespaces on-the-fly using the nvmet target
driver and then the Nova compute node nvme connects to these NVM sets
and attaches them to the VM instances.

Thanks.
Sushil.













On Wed, Nov 20, 2019 at 8:59 PM Keith Busch <kbusch@kernel.org> wrote:
>
> On Wed, Nov 20, 2019 at 01:58:29PM +0530, Sushil wrote:
> > Hi All,
> >
> > Are NVM Sets supported on Linux (Endurance, PLM etc)?
> > I could find the userspace command option "id-nvmset" (and the ioctl
> > NVME_ID_CNS_NVMSET_LIST) in the nvme-cli,
> > but nothing in the Linux kernel host and target.
>
> It makes sense for an admin to query this kind of thing, so tooling
> has support for that. It could possibly make sense for the target to
> implement sets if it can determine that two namespace resources are
> independent from each other, but what do you want the host driver to do
> with that information?

_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  reply	other threads:[~2019-11-20 18:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-20  8:28 NVM Sets supported on Linux? Sushil
2019-11-20 15:29 ` Keith Busch
2019-11-20 18:03   ` Sushil [this message]
2019-11-20 18:21     ` Keith Busch
2019-11-20 19:22       ` Sushil
2019-11-21  0:04         ` Chaitanya Kulkarni

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=CAOoKxP8XWhuF7ROKsTHmUpsaUvwCJS0ZH7xOXJGUKQvqUOrU+Q@mail.gmail.com \
    --to=sushil32@gmail.com \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    /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).