Re: [dpdk-dev] [PATCH] eal: Place EAL thread stack in a reserved per-lcore memzone

2020-04-27 Thread Pavan Nikhilesh Bhagavatula
> lib/librte_eal/linux/eal.c | 20 > 1 file changed, 20 insertions(+) > >diff --git a/lib/librte_eal/linux/eal.c b/lib/librte_eal/linux/eal.c >index 9530ee5..e047107 100644 >--- a/lib/librte_eal/linux/eal.c >+++ b/lib/librte_eal/linux/eal.c >@@ -68,6 +68,8 @@ > > #define KERNEL

Re: [dpdk-dev] [PATCH] eal: Place EAL thread stack in a reserved per-lcore memzone

2020-04-14 Thread Ananyev, Konstantin
Hi, > > Reserve a per-lcore 4MB memzone and allocate thread stack of EAL threads > there for better NUMA locality of stack-allocated variables I wonder if there any real performance improvement seen with that change? Any case (existing DPDK app/example) that can demonstrate it? Konstantin >

Re: [dpdk-dev] [PATCH] eal: Place EAL thread stack in a reserved per-lcore memzone

2020-04-13 Thread Jerin Jacob
On Mon, Apr 13, 2020 at 2:39 PM Christos Ricudis wrote: > > Reserve a per-lcore 4MB memzone and allocate thread stack of EAL threads > there for better NUMA locality of stack-allocated variables It looks like a good idea to me. Some questions/feedback. 1) It is better to get the stack size fro

[dpdk-dev] [PATCH] eal: Place EAL thread stack in a reserved per-lcore memzone

2020-04-13 Thread Christos Ricudis
Reserve a per-lcore 4MB memzone and allocate thread stack of EAL threads there for better NUMA locality of stack-allocated variables Signed-off-by: Christos Ricudis --- lib/librte_eal/linux/eal.c | 20 1 file changed, 20 insertions(+) diff --git a/lib/librte_eal/linux/eal.