Re: [dpdk-dev] [PATCH 13/41] eal: replace memseg with memseg lists

2018-03-20 Thread Burakov, Anatoly
On 19-Mar-18 5:39 PM, Olivier Matz wrote: On Sat, Mar 03, 2018 at 01:46:01PM +, Anatoly Burakov wrote: [...] --- a/config/common_base +++ b/config/common_base @@ -61,7 +61,20 @@ CONFIG_RTE_CACHE_LINE_SIZE=64 CONFIG_RTE_LIBRTE_EAL=y CONFIG_RTE_MAX_LCORE=128 CONFIG_RTE_MAX_NUMA_NODES=8

Re: [dpdk-dev] [PATCH 13/41] eal: replace memseg with memseg lists

2018-03-19 Thread Olivier Matz
On Sat, Mar 03, 2018 at 01:46:01PM +, Anatoly Burakov wrote: [...] > --- a/config/common_base > +++ b/config/common_base > @@ -61,7 +61,20 @@ CONFIG_RTE_CACHE_LINE_SIZE=64 > CONFIG_RTE_LIBRTE_EAL=y > CONFIG_RTE_MAX_LCORE=128 > CONFIG_RTE_MAX_NUMA_NODES=8 > -CONFIG_RTE_MAX_MEMSEG=256 > +CON

[dpdk-dev] [PATCH 13/41] eal: replace memseg with memseg lists

2018-03-03 Thread Anatoly Burakov
Before, we were aggregating multiple pages into one memseg, so the number of memsegs was small. Now, each page gets its own memseg, so the list of memsegs is huge. To accommodate the new memseg list size and to keep the under-the-hood workings sane, the memseg list is now not just a single list, bu