patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: dev@dpdk.org, Kevin Traynor <ktraynor@redhat.com>,
	John McNamara <john.mcnamara@intel.com>,
	Marko Kovacevic <marko.kovacevic@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] doc: document libnuma requirement for NUMA systems
Date: Fri, 01 Feb 2019 11:51:08 +0100	[thread overview]
Message-ID: <1601229.0ZU4WC4zjU@xps> (raw)
In-Reply-To: <bf5f4f4e-6415-71d2-5e47-501634613d8d@intel.com>

01/02/2019 11:28, Burakov, Anatoly:
> On 31-Jan-19 6:14 PM, Kevin Traynor wrote:
> > On 01/31/2019 05:05 PM, Anatoly Burakov wrote:
> >> Since 18.05, libnuma is pretty much required on Linux when using
> >> non-legacy mode, because without it, we cannot know where our
> >> hugepages are located [1].
> >>
> >> In legacy mode, libnuma is not required because we can still sort
> >> pages by sockets, as we use pagemap lookup method to figure out
> >> socket ID's for pages.
> >>
> >> So, document libnuma as required for NUMA systems and non-legacy
> >> mode.
> >>
> >> [1] https://mails.dpdk.org/archives/dev/2018-December/120490.html
> >>
> > 
> > Might as well add to the stable docs also. Picking this commit as it's
> > where both mode are available
> > 
> > Fixes: 6b42f75632f0 ("eal: enable non-legacy memory mode")
> > Cc: stable@dpdk.org
> 
> Yup, thought of that right after leaving office yesterday! :)

Applied, thanks

      reply	other threads:[~2019-02-01 10:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <93e6481f516c2549308e0745388a0bd80b44e783.1548954304.git.anatoly.burakov@intel.com>
2019-01-31 18:14 ` Kevin Traynor
2019-02-01 10:28   ` Burakov, Anatoly
2019-02-01 10:51     ` Thomas Monjalon [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=1601229.0ZU4WC4zjU@xps \
    --to=thomas@monjalon.net \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=ktraynor@redhat.com \
    --cc=marko.kovacevic@intel.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).