From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from dpdk.org (dpdk.org [92.243.14.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 07C74A04DD;
	Tue, 31 Dec 2019 08:57:54 +0100 (CET)
Received: from [92.243.14.124] (localhost [127.0.0.1])
	by dpdk.org (Postfix) with ESMTP id 3079F1C020;
	Tue, 31 Dec 2019 08:57:53 +0100 (CET)
Received: from inbox.dpdk.org (xvm-172-178.dc0.ghst.net [95.142.172.178])
 by dpdk.org (Postfix) with ESMTP id 8020F1C00D
 for <dev@dpdk.org>; Tue, 31 Dec 2019 08:57:51 +0100 (CET)
Received: by inbox.dpdk.org (Postfix, from userid 33)
 id 5FA81A04F3; Tue, 31 Dec 2019 08:57:51 +0100 (CET)
From: bugzilla@dpdk.org
To: dev@dpdk.org
Date: Tue, 31 Dec 2019 07:57:50 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: DPDK
X-Bugzilla-Component: core
X-Bugzilla-Version: 18.11
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: major
X-Bugzilla-Who: chuqifang@hisilicon.com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: dev@dpdk.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
 op_sys bug_status bug_severity priority component assigned_to reporter
 target_milestone
Message-ID: <bug-378-3@http.bugs.dpdk.org/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.dpdk.org/
Auto-Submitted: auto-generated
X-Auto-Response-Suppress: All
MIME-Version: 1.0
Subject: [dpdk-dev] [Bug 378] takes more than 500ms to allocate memory from
 a certain heap
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

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

            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 =3D heap_alloc(heap, type, size, flags, align, bound,
contig);

                /* this should have succeeded */
                if (ret =3D=3D 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.=20

our program has 64 threads which all can get memory from dpdk(hugepagesz=3D=
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 t=
han
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?

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