From: bugzilla@dpdk.org
To: spp@dpdk.org
Subject: [spp] [Bug 443] spp primary takes up the complete hugepages
Date: Thu, 23 Apr 2020 02:23:48 +0000 [thread overview]
Message-ID: <bug-443-394-5bDjzqn9FM@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-443-394@http.bugs.dpdk.org/>
https://bugs.dpdk.org/show_bug.cgi?id=443
--- Comment #11 from Vipin Varghese (vipin.varghese@intel.com) ---
Hi Hideyuki,
thanks for your updates. Summarizing your findings
1. The issue can be reproduced.
2. The parameter ```--socket-mem=100,100 --socket-limit=10,10 ``` did not make
difference for you.
My Answers
1. you can move the status of the bug to `confirmed`.
2. The parameter usage ```--socket-mem=100,100 --socket-limit=10,10``` is not
correct.
Let me explain:
a. option ```socket-mem`` defines the minimum amount memory to be used form
huge page.
b. option ```socket-limit``` defines the max limit the memory to be used from
huge page.
Hence if you want to use memory from
1. NUMA-0, it should be ```--socket-limit=100,1 --socket-mem=1024,1```
2. NUMA-1, it should be ```--socket-limit=1,100 --socket-mem=1,1024```
3. NUMA-0 and NUMA-1, it should be ```--socket-limit=100,100
--socket-mem=1024,1024```
This prevents primary or secondaries hijacking huge pages beyond
```socket-limit```
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-04-23 2:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 6:25 bugzilla
2020-04-07 8:29 ` bugzilla
2020-04-07 10:33 ` bugzilla
2020-04-08 8:23 ` bugzilla
2020-04-09 8:41 ` bugzilla
2020-04-09 10:20 ` bugzilla
2020-04-17 8:25 ` bugzilla
2020-04-19 6:50 ` bugzilla
2020-04-19 6:55 ` bugzilla
2020-04-19 6:56 ` bugzilla
2020-04-19 6:56 ` bugzilla
2020-04-23 2:00 ` bugzilla
2020-04-23 2:23 ` bugzilla [this message]
2020-04-28 4:06 ` bugzilla
2020-07-10 7:24 ` bugzilla
2020-07-20 1:12 ` bugzilla
2020-07-28 4:00 ` bugzilla
2020-07-29 0:47 ` bugzilla
2020-08-03 1:56 ` bugzilla
2020-08-03 4:49 ` bugzilla
2020-08-04 0:27 ` bugzilla
2020-08-04 1:47 ` bugzilla
2020-08-05 4:55 ` bugzilla
2020-08-05 5:52 ` bugzilla
2020-08-20 2:15 ` bugzilla
2020-08-25 11:53 ` bugzilla
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-443-394-5bDjzqn9FM@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=spp@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).