Linux PCI subsystem development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Josh Triplett" <josh@joshtriplett.org>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH] pci: Support preferring MMCONFIG for all config space accesses
Date: Tue, 27 Oct 2026 08:20:24 +0000	[thread overview]
Message-ID: <sashiko-outbox-186281@kernel.org> (raw)
In-Reply-To: <a7d2b402784a409f5564c1fdce77a41e09f29280.1793087687.git.josh@joshtriplett.org>

> Even when MMCONFIG is available, PCIe currently defaults to IO-based
> accesses for the first 256 bytes of config space.
> 
> IO-based accesses are serialized, and can cause substantial scalability
> issues when initializing a large number of devices on a system with many
> CPUs. (Those often coincide, because many systems have PCIe devices per
> CPU.)
> 
> Add a `pci=prefer_mmconf` option to use MMCONFIG for all config space
> accesses. Also add a Kconfig option (default n) to make that the
> default, allowing a boot-time opt out with `pci=no_prefer_mmconf`.
> 
> Tested on an AWS c8i.48xlarge system, with 192 CPUs, over five boots
> with and five boots without.
> 
> Without:
> PCI init 266ms
> Boot to minimal /init 726ms
> 
> With:
> PCI init 213ms (~20% faster)
> Boot to minimal /init 661ms (~9% faster)
> 
> Signed-off-by: Josh Triplett <josh@joshtriplett.org>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/a7d2b402784a409f5564c1fdce77a41e09f29280.1793087687.git.josh@joshtriplett.org?part=1


      reply	other threads:[~2026-10-27  8:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-27  8:14 [PATCH] pci: Support preferring MMCONFIG for all config space accesses Josh Triplett
2026-10-27  8:20 ` sashiko-bot [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=sashiko-outbox-186281@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=josh@joshtriplett.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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