From: minwoo.im.dev@gmail.com (Minwoo Im)
Subject: [PATCH 4/4] nvme: lightnvm: trace opcode name of I/O commands for 2.0
Date: Sun, 28 Jul 2019 12:15:44 +0900 [thread overview]
Message-ID: <20190728031544.GB24390@minwoo-desktop> (raw)
In-Reply-To: <97cbcbd3-5887-ec8e-dd43-ef08d612372c@lightnvm.io>
Hi Matias,
> It can not be assumed that it is an nvme opcode for any other device than an
> OCSSD 2.0 device (the command opcodes are allocated from the vendor-specific
> range of the NVMe specification). The trace code should be updated to take
> that into account before using the lookup value.
Okay!
> As a side note, I appreciate the work being put into supporting OCSSD, but
> for broad adoption, the OCSSD interface is superseded by the Zoned
> Namespaces (ZNS) technical proposal that is under standardization in the
> NVMe workgroup. We do expect a lot of adoption in this area, and have the
> kernel code ready when work is ratified (only at that point is the TBD
> values allocated). I hope that the energy that is now being put into OCSSD,
> can be put onto ZNS, as that is where we will see broad adoption and
> long-term support in the kernel.
Sure, Once it gets ratified, that would be great to put the energy on
it. Thanks for the info, Matias.
Thanks!
prev parent reply other threads:[~2019-07-28 3:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-27 18:41 [PATCH 0/4] nvme: update way to get qid in trace Minwoo Im
2019-07-27 18:41 ` [PATCH 1/4] nvme: simplify nvme_req_qid() Minwoo Im
2019-07-27 18:41 ` [PATCH 2/4] nvme: check admin queue with ctrl->admin_q, not rq_disk Minwoo Im
2019-07-27 18:41 ` [PATCH 3/4] nvme: lightnvm: trace opcode name Minwoo Im
2019-07-27 19:36 ` Matias Bjørling
2019-07-28 3:12 ` Minwoo Im
2019-07-27 18:41 ` [PATCH 4/4] nvme: lightnvm: trace opcode name of I/O commands for 2.0 Minwoo Im
2019-07-27 19:47 ` Matias Bjørling
2019-07-28 3:15 ` 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=20190728031544.GB24390@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