From: bugzilla@dpdk.org
To: spp@dpdk.org
Subject: [spp] [Bug 443] spp primary takes up the complete hugepages
Date: Wed, 05 Aug 2020 04:55:50 +0000 [thread overview]
Message-ID: <bug-443-394-iRRGLRhnOB@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 #21 from Hideyuki Yamashita (yamashita.hideyuki@ntt-tx.co.jp) ---
Hello Vipin,
I understand that this ticket is related with "hugepage usage"
as ticket title tells.
I understand that hugepage usage does NOT increase
regardless of number of secondary process.
The following is the result
- hugepage in system is 16G
- primary uses 8G in node0 and 8G in node1
- two secondary processes can start without increasing hugapage usage
What is the problem?
tx_h-yamashita@R730n10:~$ grep HugePages_ /proc/meminfo
HugePages_Total: 16
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
tx_h-yamashita@R730n10:~$ numastat -p spp_
Per-node process memory usage (in MBs)
tx_h-yamashita@R730n10:~$ sudo numastat -p spp_
[sudo] password for tx_h-yamashita:
Per-node process memory usage (in MBs)
PID Node 0 Node 1 Total
------------------- --------------- --------------- ---------------
36244 (sudo) 1.23 6.30 7.53
36245 (spp_primary) 8196.33 8203.80 16400.13
36255 (sudo) 0.20 9.52 9.73
------------------- --------------- --------------- ---------------
Total 8197.76 8219.62 16417.38
tx_h-yamashita@R730n10:~$
tx_h-yamashita@R730n10:~$
tx_h-yamashita@R730n10:~$
tx_h-yamashita@R730n10:~$
tx_h-yamashita@R730n10:~$
tx_h-yamashita@R730n10:~$
tx_h-yamashita@R730n10:~$ grep HugePages_ /proc/meminfo
HugePages_Total: 16
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
tx_h-yamashita@R730n10:~$ sudo numastat -p spp_
Per-node process memory usage (in MBs)
PID Node 0 Node 1 Total
------------------- --------------- --------------- ---------------
36244 (sudo) 1.23 6.30 7.53
36245 (spp_primary) 8196.33 8203.80 16400.13
36261 (sudo) 0.20 9.52 9.71
36262 (spp_nfv) 8206.14 8194.36 16400.50
36267 (sudo) 0.33 7.02 7.34
------------------- --------------- --------------- ---------------
Total 16404.22 16420.99 32825.21
tx_h-yamashita@R730n10:~$
tx_h-yamashita@R730n10:~$
tx_h-yamashita@R730n10:~$
tx_h-yamashita@R730n10:~$
tx_h-yamashita@R730n10:~$
tx_h-yamashita@R730n10:~$
tx_h-yamashita@R730n10:~$ grep HugePages_ /proc/meminfo
HugePages_Total: 16
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
tx_h-yamashita@R730n10:~$ sudo numastat -p spp_
Per-node process memory usage (in MBs)
PID Node 0 Node 1 Total
------------------- --------------- --------------- ---------------
36244 (sudo) 1.23 6.30 7.53
36245 (spp_primary) 8196.33 8203.80 16400.13
36261 (sudo) 0.20 9.52 9.71
36262 (spp_nfv) 8206.14 8194.36 16400.50
36273 (sudo) 0.20 9.68 9.89
36274 (spp_nfv) 8206.15 8194.17 16400.32
36279 (sudo) 1.23 6.29 7.52
------------------- --------------- --------------- ---------------
Total 24611.48 24624.12 49235.60
tx_h-yamashita@R730n10:~$
BR,
Hideyuki Yamashita
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-08-05 4:55 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
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 [this message]
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-iRRGLRhnOB@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).