From: Luca Boccassi <bluca@debian.org>
To: David Marchand <david.marchand@redhat.com>, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH 17.11] eal: remove dead code on NUMA node detection
Date: Tue, 07 Jan 2020 11:27:10 +0000 [thread overview]
Message-ID: <b33c90e5c0d4713ac3edc9c439dc43c0ff083614.camel@debian.org> (raw)
In-Reply-To: <20200103111340.25760-1-david.marchand@redhat.com>
On Fri, 2020-01-03 at 12:13 +0100, David Marchand wrote:
> [ upstream commit 8e35792c5325f9fd2cb7cfab507aa23fc956ced7 ]
>
> RTE_EAL_ALLOW_INV_SOCKET_ID had been introduced and documented as
> used
> with xen dom0 support (dropped for some time now).
>
> Closely looking at this, the code was changed later and ensures that
> the
> socket id is in the [0..RTE_MAX_NUMA_NODES] range anyway.
>
> Let's drop this dead code and the build option with it.
>
> Fixes: 94ef2964148a ("eal/linux: fix numa node detection")
>
> Acked-by: Stephen Hemminger <stephen@networkplumber.org>
> Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
> config/common_base | 1 -
> lib/librte_eal/common/eal_common_lcore.c | 11 -----------
> 2 files changed, 12 deletions(-)
Thanks, applied
--
Kind regards,
Luca Boccassi
prev parent reply other threads:[~2020-01-07 11:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-03 11:13 David Marchand
2020-01-07 11:27 ` Luca Boccassi [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=b33c90e5c0d4713ac3edc9c439dc43c0ff083614.camel@debian.org \
--to=bluca@debian.org \
--cc=david.marchand@redhat.com \
--cc=stable@dpdk.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).