Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: minwoo.im.dev@gmail.com (Minwoo Im)
Subject: [PATCH 5/5] lnvm: introduce alias geometry for id-ns for lnvm
Date: Thu, 25 Jul 2019 22:53:54 +0900	[thread overview]
Message-ID: <20190725135354.GE3018@minwoo-desktop> (raw)
In-Reply-To: <519420f6-350d-05e9-4938-45bc529b9a26@lightnvm.io>

Hi Matias,

On 19-07-24 14:29:38, Matias Bj?rling wrote:
> On 23/07/2019 20.36, Minwoo Im wrote:
> > Now we have 2.0 OCSSD spec which introudces Geometry command instead of
> > Identity or something else.  This patch just adds an alias for this
> > command for the given NVMe namespace with backward compatibility.
> > 
> > Cc: Keith Busch <kbusch at kernel.org>
> > Cc: Matias Bjorling <mb at lightnvm.io>
> > Signed-off-by: Minwoo Im <minwoo.im.dev at gmail.com>
> > ---
> >   plugins/lnvm/lnvm-nvme.h | 2 +-
> >   1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/plugins/lnvm/lnvm-nvme.h b/plugins/lnvm/lnvm-nvme.h
> > index f091f7b..2879a0b 100644
> > --- a/plugins/lnvm/lnvm-nvme.h
> > +++ b/plugins/lnvm/lnvm-nvme.h
> > @@ -11,7 +11,7 @@ PLUGIN(NAME("lnvm", "LightNVM specific extensions"),
> >   	COMMAND_LIST(
> >   		ENTRY("list", "List available LightNVM devices", lnvm_list)
> >   		ENTRY("info", "List general information and available target engines", lnvm_info)
> > -		ENTRY("id-ns", "List geometry for LightNVM device", lnvm_id_ns)
> > +		ENTRY("id-ns", "List geometry for LightNVM device", lnvm_id_ns, "geometry")
> >   		ENTRY("chunk-log", "Chunk information by Get Log Page", lnvm_chunk_log)
> >   		ENTRY("init", "Initialize media manager on LightNVM device", lnvm_init)
> >   		ENTRY("create", "Create target on top of a LightNVM device", lnvm_create_tgt)
> 
> Hi Minwoo,
> 
> How about also rewording the text to:
> 
> List geometry structure for LightNVM device?

No problem with that.  Not a native speaker so always welcome this kind
of review :)

> Also, do we want to use a short hand (instead of writing geometry in full)?

You mean like "geo" or something like this?

> How is it done elsewhere in the nvme-cli code?

Actually only place that has this kind of _alias_ is fw-commit
subcommand:

```c
	ENTRY("fw-commit", "Verify and commit firmware to a specific slot (fw-activate in old version < 1.2)", fw_commit, "fw-activate")
```

The firmware commit command has been renamed to "fw-activate" so that
this kind of alias has been applied.

But in this patch's case, I just wanted to make sure that the "id-ns"
subcommand is for Geometry command that what the SPEC exactly says.

You have any other words in your mind?  It would be great if you can
propose here :)  OR do you want it as it is with "id-ns" only?

> Regards,
> 
> Matias
> 

Thanks!

      reply	other threads:[~2019-07-25 13:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-23 18:35 [PATCH 0/5] nvme-cli: lnvm: introduce chunk-log command Minwoo Im
2019-07-23 18:35 ` [PATCH 1/5] lnvm: make data_len to sizeof() instead of magic number Minwoo Im
2019-07-24  7:14   ` Javier González
2019-07-24 12:33   ` Matias Bjørling
2019-07-25 13:46     ` Minwoo Im
2019-07-23 18:35 ` [PATCH 2/5] lnvm: export lnvm_get_identity Minwoo Im
2019-07-24  7:24   ` Javier González
2019-07-23 18:35 ` [PATCH 3/5] lnvm: add chunk_info log page structure Minwoo Im
2019-07-23 18:36 ` [PATCH 4/5] lnvm: introduce chunk-log command for chunk info Minwoo Im
2019-07-24  7:22   ` Javier González
2019-07-25 13:37     ` Minwoo Im
2019-07-25 13:53       ` Javier González
2019-07-24 12:27   ` Matias Bjørling
2019-07-25 13:43     ` Minwoo Im
2019-07-25 15:29     ` Minwoo Im
2019-07-27 15:25       ` Matias Bjørling
2019-07-27 17:55         ` Minwoo Im
2019-07-23 18:36 ` [PATCH 5/5] lnvm: introduce alias geometry for id-ns for lnvm Minwoo Im
2019-07-24 12:29   ` Matias Bjørling
2019-07-25 13:53     ` Minwoo Im [this message]

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=20190725135354.GE3018@minwoo-desktop \
    --to=minwoo.im.dev@gmail.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