DPDK usage discussions
 help / color / mirror / Atom feed
* [dpdk-users] Is legacy-mem mode perform worse than default hugepage mode?
@ 2020-05-09  8:23 zhuhengbo
  0 siblings, 0 replies; only message in thread
From: zhuhengbo @ 2020-05-09  8:23 UTC (permalink / raw)
  To: users

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb2312", Size: 402 bytes --]


         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

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2020-05-09  8:24 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-05-09  8:23 [dpdk-users] Is legacy-mem mode perform worse than default hugepage mode? zhuhengbo

DPDK usage discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ https://inbox.dpdk.org/users \
	public-inbox-index users

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git