From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <kbusch@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
santhosh kumar <santhu.linux@gmail.com>,
linux-kernel@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Ming Lei <ming.lei@redhat.com>,
x86@kernel.org
Subject: Re: [RFC] PCI_IRQ_AFFINITY limits MSI-X allocation on 384 CPU / 1000+ NVMe system
Date: Tue, 4 Aug 2026 16:10:23 +0200 [thread overview]
Message-ID: <20260804141023.GA9171@lst.de> (raw)
In-Reply-To: <anC3P7QCS46WGDo5@kbusch-mbp>
On Mon, Aug 03, 2026 at 05:43:59AM -1000, Keith Busch wrote:
> On Thu, Jul 30, 2026 at 09:44:21PM +0200, Thomas Gleixner wrote:
> > On Thu, Jul 30 2026 at 07:28, Keith Busch wrote:
> > > We can introduce a module parameter to throttle down the maximum number
> > > of IO queues to allocate per controller. I don't think the driver can
> > > automatically reason out what the correct number should be because it
> > > doesn't know how many devices it's going to see.
> >
> > I might be missing something here as usual, but the number of io queues
> > per controller does not affect that at all as I explained before.
>
> Oh, you did explain that. I skipped to the end as I had too many
> distractions last week. Sorry about that, and thanks for the
> re-explanation.
>
> I mistakenly was thinking the effective_affinity was the only hardware
> resource used. Back to the drawing board.
But given that we don't use multiple tag_set by default this can't
be the issue of the reported unless they didnt report enabling
multiple tag sets.
next prev parent reply other threads:[~2026-08-04 14:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 6:42 [RFC] PCI_IRQ_AFFINITY limits MSI-X allocation on 384 CPU / 1000+ NVMe system santhosh kumar
2026-07-28 22:52 ` Thomas Gleixner
2026-07-29 6:29 ` santhosh kumar
2026-07-30 13:16 ` Thomas Gleixner
2026-07-30 13:28 ` Keith Busch
2026-07-30 19:44 ` Thomas Gleixner
2026-08-03 15:43 ` Keith Busch
2026-08-04 14:10 ` Christoph Hellwig [this message]
2026-08-04 14:56 ` Keith Busch
2026-08-04 21:27 ` Thomas Gleixner
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=20260804141023.GA9171@lst.de \
--to=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=santhu.linux@gmail.com \
--cc=tglx@linutronix.de \
--cc=x86@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