Re: [dpdk-dev] [PATCH] mem: fix free segment when using huge-unlink option

On Mon, Feb 22, 2021 at 5:53 PM Burakov, Anatoly wrote: > On 22-Feb-21 10:41 AM, Roy Shterman wrote: > > When using huge_unlink we unlink the segment right > > after allocation. Although we unlink the file we keep > > the fd in fd_list so file still exist just the path dele

[dpdk-dev] [PATCH] mem: fix free segment when using huge-unlink option

iling rte_malloc() although we have hugepages available. Fixes: d435aad37da7 ("mem: support --huge-unlink mode") Signed-off-by: Roy Shterman --- lib/librte_eal/linux/eal_memalloc.c | 14 ++ 1 file changed, 2 insertions(+), 12 deletions(-) diff --git a/lib/librte_eal/linux/eal_me

[dpdk-dev] What is the impact of RTE_FORCE_INTRINSIC on performance

Hi, I'm running DPDK on Intel x86 processor which supports SSE2, in my current deployment I didn't enabled RTE_FORCE_INTRINSIC. After reading on Intel's intrinsic pause I wonder if I should enable it or not. especially how it should impact on latency those noop command going through the CPU. Also

Re: [dpdk-dev] Question about cache_size in rte_mempool_create

>> On 24/11/17 11:30, Bruce Richardson wrote: >>>> On Thu, Nov 23, 2017 at 11:05:11PM +0200, Roy Shterman wrote: >>>> Hi, >>>> >>>> In the documentation it says that: >>>> >>>> * @param cache_size >>>> * If cac

[dpdk-dev] Question about cache_size in rte_mempool_create

Hi, In the documentation it says that: * @param cache_size * If cache_size is non-zero, the rte_mempool library will try to * limit the accesses to the common lockless pool, by maintaining a * per-lcore object cache. This argument must be lower or equal to * CONFIG_RTE_MEMPOOL_CACHE_