From: minwoo.im.dev@gmail.com (Minwoo Im)
Subject: [PATCH 4/5] lnvm: introduce chunk-log command for chunk info
Date: Thu, 25 Jul 2019 22:43:32 +0900 [thread overview]
Message-ID: <20190725134332.GC3018@minwoo-desktop> (raw)
In-Reply-To: <a40ea502-e293-e07c-9f7b-e5f9cc118adf@lightnvm.io>
Hi Matias,
On 19-07-24 14:27:10, Matias Bj?rling wrote:
> On 23/07/2019 20.36, Minwoo Im wrote:
> > To retrieve the chunk information from the nvme namespae for the given
> > OCSSD, we can just do like:
> > nvme lnvm chunk-log /dev/nvme0n1 --output-format=normal
> >
> > This will calculate the data length from the geometry data structure
> > which might be retrieved by a Geometry command(Identity for 1.2 spec.).
> > Then it will request get log page API for 1.3 NVMe spec to get the
> > entries which indicate chunk information.
> >
> > 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>
> > ---
> > diff --git a/plugins/lnvm/lnvm-nvme.h b/plugins/lnvm/lnvm-nvme.h
> > index 3d5cbc5..f091f7b 100644
> > --- a/plugins/lnvm/lnvm-nvme.h
> > +++ b/plugins/lnvm/lnvm-nvme.h
> > @@ -12,6 +12,7 @@ PLUGIN(NAME("lnvm", "LightNVM specific extensions"),
> > 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("chunk-log", "Chunk information by Get Log Page", lnvm_chunk_log)
>
> Chunk Information Log Page ?
Sure, I'm fine with that also.
> > ENTRY("init", "Initialize media manager on LightNVM device", lnvm_init)
> > ENTRY("create", "Create target on top of a LightNVM device", lnvm_create_tgt)
> > ENTRY("remove", "Remove target from device", lnvm_remove_tgt)
>
> Hi Minwoo,
>
> Could you squash patch 2, 3 and 4 together (4 being the main patch) - They
> belong together to implement one feature.
>
> As a side-note, we have the same command for ZNS (that will be pushed when
> the ZNS TP is ratified) - In that, we've also added support for supplying
> start lba and number of chunks (zones) to return. Could you add that as well
> to this? Then there is coherency between the two?
Thanks for the review. Yes I will if the TP has been ratified. Also
I'll prepare a new series with squashed what you just mentioned here :)
Thanks!
next prev parent reply other threads:[~2019-07-25 13:43 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 [this message]
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
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=20190725134332.GC3018@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