All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrey Kuzmin <andrey.v.kuzmin at gmail.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Nvmf target namespace specification
Date: Fri, 04 May 2018 17:56:34 +0000	[thread overview]
Message-ID: <CANvN+ekNNiKhh9x09dRL6CwMHM-v-e9heKo5ExZ0qBQ8_ZEN2w@mail.gmail.com> (raw)
In-Reply-To: A5F28D4A728A7E41839CDC5C3B5A01E8B5C96863@FMSMSX103.amr.corp.intel.com

[-- Attachment #1: Type: text/plain, Size: 2196 bytes --]

Thanks for the quick turnaround, Daniel.

On Fri, May 4, 2018, 20:48 Verkamp, Daniel <daniel.verkamp(a)intel.com> wrote:

> Hi Andrey,
>
> Do you mean on the host (initiator) side, bdev/nvme?  When you are
> connecting to a NVMe-oF target with the NVMe bdev (either via the [Nvme]
> configuration file section or the construct_nvme_bdev RPC method), you are
> specifying the address to a subsystem, and all namespaces in that subsystem
> will be exposed as bdevs.  There is currently no way to specify just a
> single namespace within the subsystem, but we could probably add this if
> there is a reasonable use case that requires it.
>

I don't think it as strong as required, but the case that has triggered my
question above was trying to run bdevperf with its target device
specification against a specific namespace at thee nvmf target.

As is (with effectively just the controller specified), it actually runs
prerry well, but I assume it does so against all namespaces the target
exports via the specified subsystem.

Regards,
Andrey

>
> If you are talking about the target side, you can configure namespaces to
> have a particular ID using the optional second parameter to the Namespace
> line in the [SubsystemN] config sections, or via the optional
> namespace.nsid parameter to the nvmf_subsystem_add_ns RPC method.
>
> Thanks,
> -- Daniel
>
> > -----Original Message-----
> > From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Andrey Kuzmin
> > Sent: Friday, May 4, 2018 10:35 AM
> > To: Storage Performance Development Kit <spdk(a)lists.01.org>
> > Subject: [SPDK] Nvmf target namespace specification
> >
> > Spdk nvmf docs suggest nvmf targets to be specified via
> > traddr/addrfam/traddr/trsvcid tuple. Is there any way to specify the
> > target controller namespace as well?
> >
> > Regards,
> > Andrey
> > _______________________________________________
> > SPDK mailing list
> > SPDK(a)lists.01.org
> > https://lists.01.org/mailman/listinfo/spdk
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk
>
-- 

Regards,
Andrey

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 3194 bytes --]

             reply	other threads:[~2018-05-04 17:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-04 17:56 Andrey Kuzmin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-05-04 19:05 [SPDK] Nvmf target namespace specification Andrey Kuzmin
2018-05-04 18:09 Walker, Benjamin
2018-05-04 17:48 Verkamp, Daniel
2018-05-04 17:34 Andrey Kuzmin

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=CANvN+ekNNiKhh9x09dRL6CwMHM-v-e9heKo5ExZ0qBQ8_ZEN2w@mail.gmail.com \
    --to=spdk@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.