From: Keith Busch <kbusch@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Fengnan <changfengnan@bytedance.com>,
Keith Busch <kbusch@meta.com>,
linux-nvme@lists.infradead.org, linux-pci@vger.kernel.org,
tglx@kernel.org, namjain@linux.microsoft.com
Subject: Re: [RFC PATCH 0/3] nvme-pci: dynamic interrupt moderation
Date: Wed, 28 Oct 2026 09:15:11 -0600 [thread overview]
Message-ID: <auIRf1QATQjVDtkH@kbusch-mbp> (raw)
In-Reply-To: <20261028150712.GA16374@lst.de>
On Wed, Oct 28, 2026 at 04:07:12PM +0100, Christoph Hellwig wrote:
> On Thu, Oct 22, 2026 at 05:43:54PM +0800, Fengnan wrote:
> > Hi Keith:
> >
> > I made some modifications to DIM and then implemented a solution
> > using the DIM framework.
> > Based on current testing, the results are now comparable to those of
> > the previous patch.
> > Here are the preliminary test results:
> > https://docs.google.com/spreadsheets/d/1e8LQPnaDhmv50XlAM3XxI0TMQkhbk0bTZwlJP1Hzzdk/edit?gid=188992110#gid=188992110
> >
> > If you agree with this approach, I’ll continue testing and optimizing.
>
> І can't speak for Keith, but I'd really love to see this going forward!
Same! This is a great problem to solve, but I'm just sorry I don't have
more cycles to work on the cause. I can quickly respin the msix noflush
pre-patches to address the naming issues tglx mentioned, and we can take
nvme in whichever direction has the best performance.
prev parent reply other threads:[~2026-10-28 15:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 22:35 [RFC PATCH 0/3] nvme-pci: dynamic interrupt moderation Keith Busch
2026-10-13 22:35 ` [RFC PATCH 1/3] genirq: Add disable_irq_nowait() Keith Busch
2026-10-13 22:46 ` sashiko-bot
2026-10-13 22:35 ` [RFC PATCH 2/3] PCI/MSI: Implement irq_mask_nowait() for MSI-x Keith Busch
2026-10-13 22:42 ` sashiko-bot
2026-10-14 17:31 ` Bjorn Helgaas
2026-10-14 21:10 ` Thomas Gleixner
2026-10-14 21:39 ` Keith Busch
2026-10-14 22:18 ` Luigi Rizzo
2026-10-13 22:35 ` [RFC PATCH 3/3] nvme-pci: hybrid irq+polling Keith Busch
2026-10-13 22:55 ` sashiko-bot
2026-10-14 7:58 ` [RFC PATCH 0/3] nvme-pci: dynamic interrupt moderation Fengnan
2026-10-22 9:43 ` Fengnan
2026-10-28 15:07 ` Christoph Hellwig
2026-10-28 15:15 ` Keith Busch [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=auIRf1QATQjVDtkH@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=changfengnan@bytedance.com \
--cc=hch@lst.de \
--cc=kbusch@meta.com \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=namjain@linux.microsoft.com \
--cc=tglx@kernel.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