From: Guixin Liu <kanie@linux.alibaba.com>
To: hch@lst.de, sagi@grimberg.me, kch@nvidia.com, d.bogdanov@yadro.com
Cc: linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvmetcli: reservation configuration support
Date: Fri, 11 Oct 2024 18:54:43 +0800 [thread overview]
Message-ID: <18ee6bc5-7025-44af-9fce-59e4fcc407cf@linux.alibaba.com> (raw)
In-Reply-To: <20241008080800.7712-1-kanie@linux.alibaba.com>
gentel ping..
Best Regards,
Guixin Liu
在 2024/10/8 16:08, Guixin Liu 写道:
> Add support for reservation configuration.
>
> Signed-off-by: Guixin Liu <kanie@linux.alibaba.com>
> ---
> nvmet/nvme.py | 2 +-
> nvmetcli | 2 ++
> 2 files changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/nvmet/nvme.py b/nvmet/nvme.py
> index 59efdb5..20b3cca 100644
> --- a/nvmet/nvme.py
> +++ b/nvmet/nvme.py
> @@ -567,7 +567,7 @@ class Namespace(CFSNode):
> if nsid < 1 or nsid > self.MAX_NSID:
> raise CFSError("NSID must be 1 to %d" % self.MAX_NSID)
>
> - self.attr_groups = ['device', 'ana']
> + self.attr_groups = ['device', 'ana', 'resv']
> self._subsystem = subsystem
> self._nsid = nsid
> self._path = "%s/namespaces/%d" % (self.subsystem.path, self.nsid)
> diff --git a/nvmetcli b/nvmetcli
> index d949891..6e5348f 100755
> --- a/nvmetcli
> +++ b/nvmetcli
> @@ -283,6 +283,8 @@ class UINamespaceNode(UINode):
> info.append("nguid=" + ns_nguid)
> if self.cfnode.grpid != 0:
> info.append("grpid=" + str(self.cfnode.grpid))
> + resv_enable = self.cfnode.get_attr("resv", "enable")
> + info.append("resv_enable=" + str(resv_enable))
> info.append("enabled" if self.cfnode.get_enable() else "disabled")
> ns_enabled = self.cfnode.get_enable()
> return (", ".join(info), True if ns_enabled == 1 else ns_enabled)
next prev parent reply other threads:[~2024-10-11 10:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 8:08 [PATCH] nvmetcli: reservation configuration support Guixin Liu
2024-10-11 10:54 ` Guixin Liu [this message]
2024-10-15 8:15 ` Guixin Liu
2024-10-15 8:17 ` Christoph Hellwig
2024-10-20 23:48 ` 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=18ee6bc5-7025-44af-9fce-59e4fcc407cf@linux.alibaba.com \
--to=kanie@linux.alibaba.com \
--cc=d.bogdanov@yadro.com \
--cc=hch@lst.de \
--cc=kch@nvidia.com \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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