From: bugzilla@dpdk.org
To: dev@dpdk.org
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.
Date: Mon, 06 Sep 2021 08:03:36 +0000 [thread overview]
Message-ID: <bug-807-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=807
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.
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
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2021-09-06 8:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-807-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.