Re: [dpdk-dev] [PATCH] doc: document libnuma requirement for NUMA systems

2019-02-01 Thread Thomas Monjalon
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]

Re: [dpdk-dev] [PATCH] doc: document libnuma requirement for NUMA systems

2019-02-01 Thread 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

Re: [dpdk-dev] [PATCH] doc: document libnuma requirement for NUMA systems

2019-01-31 Thread Kevin Traynor
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, a

[dpdk-dev] [PATCH] doc: document libnuma requirement for NUMA systems

2019-01-31 Thread Anatoly Burakov
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 fo