DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: dev@dpdk.org, Robin Jarry <rjarry@redhat.com>
Subject: Re: [PATCH v1 1/1] usertools/devbind: fix NUMA node display
Date: Thu, 28 Nov 2024 09:20:02 -0800	[thread overview]
Message-ID: <20241128092002.0ea4605c@hermes.local> (raw)
In-Reply-To: <9af1231398c4ba116d3b89164690feace37293a9.1732810125.git.anatoly.burakov@intel.com>

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?

      reply	other threads:[~2024-11-28 17:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-28 16:08 Anatoly Burakov
2024-11-28 17:20 ` Stephen Hemminger [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=20241128092002.0ea4605c@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=rjarry@redhat.com \
    /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).