From: Keith Busch <kbusch@kernel.org>
To: David Wang <00107082@163.com>
Cc: axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: nvme interrupt counters got reset after suspend/resume
Date: Wed, 19 Mar 2025 09:57:44 -0600 [thread overview]
Message-ID: <Z9rpeIsNlf6SBWi6@kbusch-mbp> (raw)
In-Reply-To: <20250319153910.18684-1-00107082@163.com>
On Wed, Mar 19, 2025 at 11:39:10PM +0800, David Wang wrote:
>
> This does not happend to counters for other interrupts on my system.
> Not sure whether this is designed explicitly this way, or happended to be this way to make suspend/resume work,
> or there is some bug behind this.
The nvme driver completely brings down the interrupts on suspend and
creates new ones on resume. They might have the same numbers and labels
on the other side of the resume, but they're not from the same original
allocation that tracks these stats. Hope that helps.
next prev parent reply other threads:[~2025-03-19 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 15:39 nvme interrupt counters got reset after suspend/resume David Wang
2025-03-19 15:57 ` Keith Busch [this message]
2025-03-19 16:23 ` David Wang
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=Z9rpeIsNlf6SBWi6@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=00107082@163.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-kernel@vger.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