From: zhuhengbo <zhuhengbo1@huawei.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] Is legacy-mem mode perform worse than default hugepage mode？
Date: Sat, 9 May 2020 08:23:55 +0000 [thread overview]
Message-ID: <8538905958B6F7489BCA5033CA2EF8E201887E94@DGGEML527-MBS.china.huawei.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb2312", Size: 402 bytes --]
Hi,all,
I have noticed that there is ¨Clegacy-mem option in dpdk init. But it¡¯s not a default choice.
In my understanding, hugepage can help decrease cpu cache miss and It affects performance a lot.
So I wonder that is legacy-mem mode perform worse than default mode£¿ Why not use legacy-mem mode as a default way to use hugepages?
Any help will be greatly appreciated
Hubble Zhu
reply other threads:[~2020-05-09 8:24 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=8538905958B6F7489BCA5033CA2EF8E201887E94@DGGEML527-MBS.china.huawei.com \
--to=zhuhengbo1@huawei.com \
--cc=users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).