From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: <dev@dpdk.org>, Robin Jarry <rjarry@redhat.com>
Subject: Re: [PATCH v1 1/1] usertools/devbind: fix NUMA node display
Date: Fri, 29 Nov 2024 10:28:34 +0100 [thread overview]
Message-ID: <120a382d-77ff-4763-bb4c-30201235ab34@intel.com> (raw)
In-Reply-To: <8263d4d6-37e1-4c0c-a86d-5cbd40916c8c@intel.com>
On 11/29/2024 10:12 AM, Burakov, Anatoly wrote:
> On 11/28/2024 6:20 PM, Stephen Hemminger wrote:
>> On Thu, 28 Nov 2024 16:08:55 +0000
>> Anatoly Burakov <anatoly.burakov@intel.com> wrote:
>>
>>> + # occasionally, system may report NUMA support but lspci will
>>> not, so we
>>> + # want to go through all devices and see if any of them do not
>>> have NUMANode
>>> + # property - this will mean it is not safe to try to access it
>>> + for device_dict in devices.values():
>>> + if "NUMANode" not in device_dict:
>>> + return False
>>
>> Any indication as to why this happens, what kernel, what device?
>
> We've had internal validation team report this happenning on VM's,
> particularly ESXi. I did not dig deeper as to what particular
> configurations cause this to happen, I didn't have a chance to reproduce
> this myself.
>
I just reproduced this on my machine by disabling NUMA support in BIOS.
I can confirm that /sys/devices/system/node exists in sysfs but lspci
will not report NUMA node in that case. So, it probably applies to all
kernels.
--
Thanks,
Anatoly
next prev parent reply other threads:[~2024-11-29 9:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 16:08 Anatoly Burakov
2024-11-28 17:20 ` Stephen Hemminger
2024-11-29 9:12 ` Burakov, Anatoly
2024-11-29 9:28 ` Burakov, Anatoly [this message]
2024-11-29 8:06 ` Robin Jarry
2024-11-29 9:52 ` Anatoly Burakov
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=120a382d-77ff-4763-bb4c-30201235ab34@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=rjarry@redhat.com \
--cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).