From: Walker, Benjamin <benjamin.walker at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] SPDK + user space appliance
Date: Wed, 31 Jan 2018 16:40:47 +0000 [thread overview]
Message-ID: <1517416845.25907.94.camel@intel.com> (raw)
In-Reply-To: 1516384132.25907.19.camel@intel.com
[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]
On Fri, 2018-01-19 at 17:48 +0000, Walker, Benjamin wrote:
> On Fri, 2018-01-19 at 17:38 +0000, Aneesh Pachilangottil wrote:
> > Hi Shahar,
> > By namespace, do you mean the namespace exposed by the
> > NVMeOF
> > target which is visible to the host? I am asking because, I am looking into
> > something similar and would like to understand whether our requirements
> > matches.
> >
> > My requirement is to add a new namespace to an existing NVMeOF subsystem
> > using
> > RPC. I don`t find an option to do this presently using RPC. When calling
> > construct_nvmf_subsystem method, we can specify the list of namespaces to be
> > created, however adding a new namespace to an already existing subsystem
> > doesn`t seems to be supported. This is what I am trying to achieve.
> >
>
> This just needs a new RPC for adding/removing a namespace. The code in
> lib/nvmf
> is already set up to handle dynamically adding and removing namespaces, we
> just
> haven't coded the RPC yet. It's on the NVMe-oF trello board https://trello.com
> /b
> /G2f3dVcs/nvme-of.
> _______________________________________________
I've uploaded some patches to add the necessary RPCs. They aren't merged quite
yet, but will be soon. See:
https://review.gerrithub.io/#/c/396696/
next reply other threads:[~2018-01-31 16:40 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 16:40 Walker, Benjamin [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-07-16 22:58 [SPDK] SPDK + user space appliance
2018-07-12 14:34 Shahar Salzman
2018-05-13 8:46 Shahar Salzman
2018-05-11 13:11
2018-05-10 13:33 Shahar Salzman
2018-05-10 7:36
2018-05-10 6:34
2018-05-09 19:45 Shahar Salzman
2018-05-09 16:52 Walker, Benjamin
2018-05-09 11:57 Shahar Salzman
2018-05-09 9:54
2018-05-09 8:43
2018-05-09 7:48 Shahar Salzman
2018-05-08 17:30 Walker, Benjamin
2018-05-08 7:36 Shahar Salzman
2018-05-07 18:18 Harris, James R
2018-05-07 18:02 Walker, Benjamin
2018-05-06 10:32 Shahar Salzman
2018-05-03 17:50 Verkamp, Daniel
2018-05-03 8:00 Shahar Salzman
2018-04-25 6:02 Shahar Salzman
2018-04-24 16:19 Walker, Benjamin
2018-04-23 15:44 Shahar Salzman
2018-02-02 21:43 Walker, Benjamin
2018-02-01 8:29 Shahar Salzman
2018-01-31 16:48 Walker, Benjamin
2018-01-25 14:19 Shahar Salzman
2018-01-23 8:21 Ilan Steinberg
2018-01-23 8:20 Ilan Steinberg
2018-01-19 17:48 Walker, Benjamin
2018-01-19 17:38 Aneesh Pachilangottil
2018-01-19 17:28 Walker, Benjamin
2018-01-18 23:53 Chang, Cunyin
2018-01-14 9:09 Shahar Salzman
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=1517416845.25907.94.camel@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox