From: Tokunori Ikegami <ikegami.t@gmail.com>
To: Keith Busch <kbusch@kernel.org>
Cc: linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvme-pci: add NVMe controller statistics
Date: Fri, 30 May 2025 02:38:39 +0900 [thread overview]
Message-ID: <9164e067-09f2-43e3-b57e-99fa2c9bd97f@gmail.com> (raw)
In-Reply-To: <aDdze52GrviTSmFj@kbusch-mbp>
On 2025/05/29 5:35, Keith Busch wrote:
> Specifically on sysfs attributes, the intended use was one file, one
> attribute, one value. That makes programatically parsing these much
> easier. So what you'd do instead is create 4 new files called
> "timeouts", "aborts", "resets", and "disables", and each just print out
> a sinlge number instead of this more complex output. If you're concerned
> with polluting the nvme device's sysfs directory, you can also make a
> sub-directory called "stats" to collect such things.
Just done as mentioned by the version patch.
> That principle hasn't always been strictly followed, but let's not
> introduce new deviants.
I see.
> As to what you're tracking and reporting here, I'm not convinced it's
> useful. It's just a snapshot of what's happened for the lifetime of that
> instance, which may not be very long.
Just changed the attributes as read-write device attribute then user can
reset the counter value if needed and accumulate the counter value on
user application.
By the way I think any unstable issue behavior caused on a drive the
statistics counters can be used to check the warning behavior cause but
it is okay as not be very long for the lifetime.
Thank you.
prev parent reply other threads:[~2025-05-29 17:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 17:02 [PATCH] nvme-pci: add NVMe controller statistics Tokunori Ikegami
2025-05-28 20:35 ` Keith Busch
2025-05-29 17:38 ` Tokunori Ikegami [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=9164e067-09f2-43e3-b57e-99fa2c9bd97f@gmail.com \
--to=ikegami.t@gmail.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
/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