[dpdk-dev] [PATCH v2] app/test: fix memory needs after RTE_MAX_LCORE was increased to 128

2014-12-11 Thread De Lara Guarch, Pablo
> -Original Message- > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > Sent: Thursday, December 11, 2014 1:11 AM > To: De Lara Guarch, Pablo > Cc: dev at dpdk.org > Subject: Re: [dpdk-dev] [PATCH v2] app/test: fix memory needs after > RTE_MAX_LCORE

[dpdk-dev] [PATCH v2] app/test: fix memory needs after RTE_MAX_LCORE was increased to 128

2014-12-11 Thread Thomas Monjalon
2014-12-10 15:40, Thomas Monjalon: > 2014-12-09 10:11, Pablo de Lara: > > Since commit b91c67e5a693211862aa7dc3b78630b4e856c2af, > > maximum number of cores is 128, which has increase > > the total memory necessary for a rte_mempool structure, > > as the per-lcore local cache has been doubled in si

[dpdk-dev] [PATCH v2] app/test: fix memory needs after RTE_MAX_LCORE was increased to 128

2014-12-10 Thread Thomas Monjalon
2014-12-09 10:11, Pablo de Lara: > Since commit b91c67e5a693211862aa7dc3b78630b4e856c2af, > maximum number of cores is 128, which has increase > the total memory necessary for a rte_mempool structure, > as the per-lcore local cache has been doubled in size. > Therefore, eal_flags unit test was brok

[dpdk-dev] [PATCH v2] app/test: fix memory needs after RTE_MAX_LCORE was increased to 128

2014-12-09 Thread Pablo de Lara
Since commit b91c67e5a693211862aa7dc3b78630b4e856c2af, maximum number of cores is 128, which has increase the total memory necessary for a rte_mempool structure, as the per-lcore local cache has been doubled in size. Therefore, eal_flags unit test was broken since it needed to use more hugepages.