From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Guixin Liu <kanie@linux.alibaba.com>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"hch@lst.de" <hch@lst.de>, "sagi@grimberg.me" <sagi@grimberg.me>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"kbusch@kernel.org" <kbusch@kernel.org>
Subject: Re: [PATCH 2/3] nvme: parse dsm command detailly when tracing
Date: Tue, 30 Jan 2024 08:05:25 +0000 [thread overview]
Message-ID: <93da3b09-7cb6-4e5a-b5b0-ced7a8542c1c@nvidia.com> (raw)
In-Reply-To: <304cc83e-72c7-4b12-b2fb-f978e331e813@linux.alibaba.com>
>> I'm really not sure if we need to decode idw/idr as I've not seen those
>> fields so far
>> used by anybody maybe I'm not aware here, but can you please provide a
>> usecase where
>> you need these fields to be decoded ?
>>
>> -ck
>
> Mostly we only use "ad" filed, but sometimes our tester will set idw/idr to
>
> see whether any errors have been reported by our target. Well this is a
>
> low-persuasive usecase, but I still insist it's better to follow the spec.
>
> Best regadrs,
>
> Guixin Liu
>
>>
But why ? do you have a valid implementation that shows clear benefits
for idw/idr ? if not I'm not sure why we need to decode these fields,
unless others think it's a good idea let's not do that.
Following spec only makes sense where there is a valid implementation
for the fields we are printing and not sure if it applies to idw/idr ...
I'm fine with AD and NR they are useful ...
-ck
next prev parent reply other threads:[~2024-01-30 8:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 8:22 [PATCH 0/3] *** nvme: add some commands tracing *** Guixin Liu
2024-01-29 8:22 ` [PATCH 1/3] nvme: add tracing of reservation commands Guixin Liu
2024-01-29 8:22 ` [PATCH 2/3] nvme: parse dsm command detailly when tracing Guixin Liu
2024-01-29 11:09 ` Chaitanya Kulkarni
2024-01-30 3:51 ` Guixin Liu
2024-01-30 8:05 ` Chaitanya Kulkarni [this message]
2024-01-30 8:35 ` Guixin Liu
2024-01-31 17:36 ` Keith Busch
2024-01-29 8:22 ` [PATCH 3/3] nvme: parse format command's lbafu " Guixin Liu
2024-01-29 11:01 ` Chaitanya Kulkarni
2024-01-30 3:37 ` Guixin Liu
-- strict thread matches above, loose matches on Subject: below --
2024-01-30 11:34 [PATCH v2 0/3] *** nvme: add some commands tracing *** Guixin Liu
2024-01-30 11:34 ` [PATCH 2/3] nvme: parse dsm command detailly when tracing Guixin Liu
2024-01-30 11:35 ` Guixin Liu
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=93da3b09-7cb6-4e5a-b5b0-ced7a8542c1c@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kanie@linux.alibaba.com \
--cc=kbusch@kernel.org \
--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