[dpdk-dev] [Bug 378] takes more than 500ms to allocate memory from a certain heap

[dpdk-dev] [Bug 378] takes more than 500ms to allocate memory from a certain heap

[bugzilla]

https://bugs.dpdk.org/show_bug.cgi?id=378

            Bug ID: 378
           Summary: takes more than 500ms to allocate memory from a
                    certain heap
           Product: DPDK
           Version: 18.11
          Hardware: ARM
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: chuqifang@hisilicon.com
  Target Milestone: ---

file: lib/librte_eal/common/malloc_heap.c
function: malloc_heap_alloc_on_heap_id

code snippet:

        if (!alloc_more_mem_on_socket(heap, size, socket_id, flags, align,
                        bound, contig)) {
                ret = heap_alloc(heap, type, size, flags, align, bound,
contig);

                /* this should have succeeded */
                if (ret == NULL)
                        RTE_LOG(ERR, EAL, "Error allocating from heap\n");
        }

alloc_more_mem_on_socket takes more than 500ms when numa node0 runs out of
memory. 

our program has 64 threads which all can get memory from dpdk(hugepagesz=1G).
our business code can not go well with such code snippet, so we remove
alloc_more_mem_on_socket in malloc_heap_alloc_on_heap_id, we test it more than
1 month, and it runs ok

so, is there any side effect when i remove alloc_more_mem_on_socket in
malloc_heap_alloc_on_heap_id?

-- 
You are receiving this mail because:
You are the assignee for the bug.