From: David Marchand <david.marchand@redhat.com>
To: Nick Connolly <nick.connolly@mayadata.io>
Cc: Nicolas Dichtel <nicolas.dichtel@6wind.com>,
Anatoly Burakov <anatoly.burakov@intel.com>,
Didier Pallard <didier.pallard@6wind.com>,
Olivier Matz <olivier.matz@6wind.com>, dev <dev@dpdk.org>,
dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH v2] mem: fix allocation failure on non-NUMA kernel
Date: Tue, 13 Oct 2020 14:01:44 +0200 [thread overview]
Message-ID: <CAJFAV8yexykxPS+gKwiAa=V7Peh64b+JwskyT4WOq-PSbLV09g@mail.gmail.com> (raw)
In-Reply-To: <ce027479-2c5d-0977-b2c7-4ea98386801a@6wind.com>
On Tue, Oct 13, 2020 at 10:00 AM Nicolas Dichtel
<nicolas.dichtel@6wind.com> wrote:
>
> Le 12/10/2020 à 21:28, Nick Connolly a écrit :
> > Running dpdk-helloworld on Linux with lib numa present,
> > but no kernel support for NUMA (CONFIG_NUMA=n) causes
> > ret_service_init() to fail with EAL: error allocating
> > rte services array.
> >
> > alloc_seg() calls get_mempolicy to verify that the allocation
> > has happened on the correct socket, but receives ENOSYS from
> > the kernel and fails the allocation.
> >
> > The allocated socket should only be verified if check_numa() is true.
> >
> > Fixes: 2a96c88be83e ("mem: ease init in a docker container")
> > Cc: nicolas.dichtel@6wind.com
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Nick Connolly <nick.connolly@mayadata.io>
> Reviewed-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
Applied, thanks Nick.
--
David Marchand
next prev parent reply other threads:[~2020-10-13 12:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 12:26 [dpdk-stable] [PATCH] " Nick Connolly
2020-08-05 13:42 ` Nicolas Dichtel
2020-08-05 14:20 ` Nick Connolly
2020-08-05 14:36 ` Nicolas Dichtel
2020-08-05 14:53 ` Nick Connolly
2020-08-05 15:13 ` Nicolas Dichtel
2020-08-05 15:21 ` Nick Connolly
2020-09-17 11:28 ` Burakov, Anatoly
2020-09-17 11:31 ` Burakov, Anatoly
2020-09-17 12:29 ` Nick Connolly
2020-09-17 12:57 ` Burakov, Anatoly
2020-09-17 13:05 ` Nick Connolly
2020-09-17 14:07 ` Burakov, Anatoly
2020-09-17 14:08 ` Nick Connolly
2020-09-17 14:18 ` Burakov, Anatoly
2020-09-17 14:19 ` Nick Connolly
2020-10-12 19:28 ` [dpdk-stable] [PATCH v2] " Nick Connolly
2020-10-13 7:59 ` Nicolas Dichtel
2020-10-13 12:01 ` David Marchand [this message]
2020-10-12 19:22 Nick Connolly
2020-10-13 9:42 ` Burakov, Anatoly
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='CAJFAV8yexykxPS+gKwiAa=V7Peh64b+JwskyT4WOq-PSbLV09g@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=didier.pallard@6wind.com \
--cc=nick.connolly@mayadata.io \
--cc=nicolas.dichtel@6wind.com \
--cc=olivier.matz@6wind.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).