DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Robin Jarry" <rjarry@redhat.com>
To: "Anatoly Burakov" <anatoly.burakov@intel.com>, <dev@dpdk.org>,
	"Stephen Hemminger" <stephen@networkplumber.org>
Subject: Re: [PATCH v1 1/1] usertools/devbind: fix NUMA node display
Date: Fri, 29 Nov 2024 09:06:52 +0100	[thread overview]
Message-ID: <D5YIAVF5Q5N6.1SZAF3S81V19D@redhat.com> (raw)
In-Reply-To: <9af1231398c4ba116d3b89164690feace37293a9.1732810125.git.anatoly.burakov@intel.com>

Anatoly Burakov, Nov 28, 2024 at 17:08:
> On some systems, even though NUMA nodes may be present in sysfs, the lspci
> command will not have NUMANode keys in them, which will cause an exception.
> Fix to check if NUMANode keys are available in lspci output before enabling
> NUMA node output.
>
> Fixes: a7d69cef8f20 ("usertools/devbind: print device NUMA node")
>
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>

Acked-by: Robin Jarry <rjarry@redhat.com>


  parent reply	other threads:[~2024-11-29  8:06 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
2024-11-29  8:06 ` Robin Jarry [this message]
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=D5YIAVF5Q5N6.1SZAF3S81V19D@redhat.com \
    --to=rjarry@redhat.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --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).