From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id DED4AA0C4D;
	Mon,  6 Sep 2021 10:03:38 +0200 (CEST)
Received: from [217.70.189.124] (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id 8000640E32;
	Mon,  6 Sep 2021 10:03:38 +0200 (CEST)
Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178])
 by mails.dpdk.org (Postfix) with ESMTP id E1F3B40C35
 for <dev@dpdk.org>; Mon,  6 Sep 2021 10:03:36 +0200 (CEST)
Received: by inbox.dpdk.org (Postfix, from userid 33)
 id C9F21A0C4E; Mon,  6 Sep 2021 10:03:36 +0200 (CEST)
From: bugzilla@dpdk.org
To: dev@dpdk.org
Date: Mon, 06 Sep 2021 08:03:36 +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: unspecified
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: major
X-Bugzilla-Who: yzhu@amperecomputing.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-807-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 807] mbuf couldn't be allocated in socket1 in
 dynmen mode, but in legency mode,
 mbuf could be allocated correctly in remote socket1.
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
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=3D807

            Bug ID: 807
           Summary: mbuf couldn't be allocated in socket1 in dynmen mode,
                    but in legency mode, mbuf could be allocated correctly
                    in remote socket1.
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: yzhu@amperecomputing.com
  Target Milestone: ---

my setup is OVS+DPDK.=20

when I configed memory in dyn mode , only
"other_config:dpdk-socket-mem=3D8192,8192"
I also configured OVS PMD core in socket1, and 2VM also in socket1, I expect
all traffic will be in socket1, and won't touch any resource in socket0, But
after I printed the dpdk's mbuf address(pkts) in virtio_dev_rx_split's
copy_mbuf_to_desc, I found  mbufs  are in socket0.

then I configure memory in legency mode. added
"other_config:dpdk-extra=3D--legacy-mem ", I checked rte_eal_hugepage_init,
eal_legacy_hugepage_init is called, and also print mbuf address in=20
virtio_dev_rx_split's copy_mbuf_to_desc.  All mbufs are in socket1, it's wh=
at
expected .

So the dyn mode couldn't correctly allocated mbuf into socket1  should be a=
 bug

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