From: Bjorn Helgaas <helgaas@kernel.org>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, Yunsheng Lin <linyunsheng@huawei.com>
Subject: Re: Linux warns `Unknown NUMA node; performance will be reduced`
Date: Tue, 3 Mar 2026 15:55:58 -0600 [thread overview]
Message-ID: <20260303215558.GA4076158@bhelgaas> (raw)
In-Reply-To: <a154f694-c48b-4b3b-809f-4b74ec86a924@molgen.mpg.de>
[+cc Yunsheng, author of ad5086108b9f,
+bcc commenters on https://bugzilla.kernel.org/show_bug.cgi?id=218951,
see the email thread at
https://lore.kernel.org/all/a154f694-c48b-4b3b-809f-4b74ec86a924@molgen.mpg.de]
On Sun, Jun 09, 2024 at 10:31:05AM +0200, Paul Menzel wrote:
> Dear Linux folks,
>
> On the servers below Linux warns:
>
> Unknown NUMA node; performance will be reduced
>
> 1. [ 0.000000] DMI: Dell Inc. PowerEdge R730/0H21J3, BIOS 2.13.0
> 05/14/2021
> 2. [ 0.000000] DMI: Dell Inc. PowerEdge R730/0H21J3, BIOS 2.2.5
> 09/06/2016
> 3. [ 0.000000] DMI: Dell Inc. PowerEdge R730xd/0WCJNT, BIOS 2.3.4
> 11/08/2016
> 4. [ 0.000000] DMI: Dell Inc. PowerEdge R910/0KYD3D, BIOS 2.10.0
> 08/29/2013
> 5. [ 0.000000] DMI: Dell Inc. PowerEdge R930/0T55KM, BIOS 2.8.1
> 01/02/2020
> 6. [ 0.000000] DMI: Dell Inc. PowerEdge T630/0NT78X, BIOS 2.5.4
> 08/17/2017
> 7. [ 0.000000] DMI: Dell Inc. PowerEdge T630/0W9WXC, BIOS 1.5.4
> 10/04/2015
> 8. [ 0.000000] DMI: Dell Inc. PowerEdge T630/0W9WXC, BIOS 2.11.0
> 12/23/2019
> 9. [ 0.000000] DMI: Dell Inc. PowerEdge T630/0W9WXC, BIOS 2.1.5
> 04/13/2016
> 10. [ 0.000000] DMI: Supermicro Super Server/X13SAE, BIOS 2.0 10/17/2022
Similar reports in the bugzilla for:
Host: VMware VM Ubuntu 24.04.1
CPU: Intel(R) Xeon(R) Silver 4310 CPU @ 2.10GHz
Kernel: 6.11.0-rc6
and
Lenovo P700 workstation
6.19.5 kernel
ad5086108b9f ("PCI: Warn if no host bridge NUMA node info") added this
"Unknown NUMA node; performance will be reduced" warning.
The problem is that firmware didn't tell us anything about which CPUs
are closest to this PCI host bridge, so we can't try to optimize by
running the driver on a CPU that's close to the device.
The kernel can't figure out this locality information itself, so
there's nothing we can really do in the kernel, and there's nothing
users can do either other than check for BIOS updates.
What if we just downgraded the message to "info"? And/or we could
reword this to be less alarming.
I guess we could even drop the message altogether and assume that
vendors will provide the locality information if there's any
meaningful performance benefit. It could be that it really doesn't
matter where drivers run on these machines, so there's no benefit to
providing the locality information.
Bjorn
next prev parent reply other threads:[~2026-03-03 21:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-09 8:31 Linux warns `Unknown NUMA node; performance will be reduced` Paul Menzel
2024-06-10 19:42 ` Bjorn Helgaas
2024-06-10 20:27 ` Paul Menzel
2024-06-11 3:05 ` Yunsheng Lin
2024-06-11 22:31 ` Bjorn Helgaas
2025-08-05 21:39 ` Paul Menzel
2024-06-11 15:11 ` Bjorn Helgaas
2024-06-18 15:19 ` Paul Menzel
2026-03-03 21:55 ` Bjorn Helgaas [this message]
2026-03-04 1:34 ` Yunsheng Lin
2026-03-04 21:18 ` Bjorn Helgaas
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=20260303215558.GA4076158@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=linyunsheng@huawei.com \
--cc=pmenzel@molgen.mpg.de \
/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