From: Christoph Hellwig <hch@lst.de>
To: changfengnan <changfengnan@bytedance.com>
Cc: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
jun1.zeng@intel.com, Guzebing <guzebing@bytedance.com>
Subject: Re: [PATCH] nvme-pci: add adaptive interrupt polling
Date: Wed, 19 Aug 2026 07:25:17 +0200 [thread overview]
Message-ID: <20260819052517.GB32364@lst.de> (raw)
In-Reply-To: <d9210bcdf73fbe1ac8b6ec132865609a3ed68688.c71e295f.cf49.450b.ad13.ed0e27cd481a@bytedance.com>
On Tue, Aug 18, 2026 at 11:53:55AM +0800, changfengnan wrote:
> 1. Regarding the NVME_ADAPTIVE_POLL_PERIOD_NS parameter, is it necessary to make it a configurable setting? Perhaps Gen6 SSDs require a smaller value? I currently do not have a testing environment for this, but the default value of 10 us appears to be sufficient for Gen4 and Gen5.
The most important thing to consider in the short term is not the fastest
possible devices, but the worst. I.e. consider what this does on really
crappy older cusomer drives, as that is probably the biggest install base
using the Linux nvme driver.
> 2. Should MSI be supported? I do not have a similar environment, so I am unsure how it would perform in such scenarios.
Or legacy interrupts :) I don't think we have to support them as long
as we cleanly disable the feature.
> 3. Should it be enabled by default? Although current tests show only a minor performance hit, I still lean toward disabling it by default and waiting to gather more test feedback.
I think it should eventually enabled by default, but I'd also be happy
to merge it fist and then flip the bit later.
next prev parent reply other threads:[~2026-08-19 5:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 3:38 [PATCH] nvme-pci: add adaptive interrupt polling Fengnan Chang
2026-08-18 3:53 ` changfengnan
2026-08-19 5:25 ` Christoph Hellwig [this message]
2026-08-19 6:33 ` changfengnan
2026-08-19 5:35 ` Christoph Hellwig
2026-08-19 7:02 ` changfengnan
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=20260819052517.GB32364@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=changfengnan@bytedance.com \
--cc=guzebing@bytedance.com \
--cc=jun1.zeng@intel.com \
--cc=kbusch@kernel.org \
--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