From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 632BA1B47B; Thu, 31 Jan 2019 19:14:56 +0100 (CET) Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 78CE82CE90A; Thu, 31 Jan 2019 18:14:55 +0000 (UTC) Received: from ktraynor.remote.csb (ovpn-117-200.ams2.redhat.com [10.36.117.200]) by smtp.corp.redhat.com (Postfix) with ESMTP id 4B50119492; Thu, 31 Jan 2019 18:14:52 +0000 (UTC) To: Anatoly Burakov , dev@dpdk.org Cc: John McNamara , Marko Kovacevic , thomas@monjalon.net, "stable@dpdk.org" References: <93e6481f516c2549308e0745388a0bd80b44e783.1548954304.git.anatoly.burakov@intel.com> From: Kevin Traynor Organization: Red Hat Message-ID: Date: Thu, 31 Jan 2019 18:14:51 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 In-Reply-To: <93e6481f516c2549308e0745388a0bd80b44e783.1548954304.git.anatoly.burakov@intel.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.29]); Thu, 31 Jan 2019 18:14:55 +0000 (UTC) Subject: Re: [dpdk-dev] [PATCH] doc: document libnuma requirement for NUMA systems X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2019 18:14:56 -0000 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 > Signed-off-by: Anatoly Burakov > --- > doc/guides/linux_gsg/sys_reqs.rst | 8 ++++++++ > 1 file changed, 8 insertions(+) > > diff --git a/doc/guides/linux_gsg/sys_reqs.rst b/doc/guides/linux_gsg/sys_reqs.rst > index 8ec3af491..23cfc27ab 100644 > --- a/doc/guides/linux_gsg/sys_reqs.rst > +++ b/doc/guides/linux_gsg/sys_reqs.rst > @@ -70,6 +70,14 @@ Compilation of the DPDK > > * libnuma-dev in Debian/Ubuntu; > > + .. note:: > + > + On systems with NUMA support, `libnuma-dev` (aka `numactl-devel`) is a > + recommended dependency when `--legacy-mem` switch is used, and a > + *required* dependency if default memory mode is used. While DPDK will > + compile and run without `libnuma` even on NUMA-enabled systems, both > + usability and performance will be degraded. > + > * Python, version 2.7+ or 3.2+, to use various helper scripts included in the DPDK package. > > > Acked-by: Kevin Traynor