Bug 807 - mbuf couldn't be allocated in socket1 in dynmen mode, but in legency mode, mbuf could be allocated correctly in remote socket1.
Summary: mbuf couldn't be allocated in socket1 in dynmen mode, but in legency mode, mb...
Status: UNCONFIRMED
Alias: None
Product: DPDK
Classification: Unclassified
Component: core (show other bugs)
Version: unspecified
Hardware: All All
: Normal major
Target Milestone: ---
Assignee: dev
URL:
Depends on:
Blocks:
 
Reported: 2021-09-06 10:03 CEST by Yuanzhang Zhu
Modified: 2021-09-06 10:03 CEST (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Yuanzhang Zhu 2021-09-06 10:03:36 CEST 
my setup is OVS+DPDK. 

when I configed memory in dyn mode , only "other_config:dpdk-socket-mem=8192,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=--legacy-mem ", I checked rte_eal_hugepage_init, eal_legacy_hugepage_init is called, and also print mbuf address in  virtio_dev_rx_split's copy_mbuf_to_desc.  All mbufs are in socket1, it's what expected .

So the dyn mode couldn't correctly allocated mbuf into socket1  should be a bug
Note You need to log in before you can comment on or make changes to this bug.