From: bugzilla@dpdk.org
To: spp@dpdk.org
Subject: [spp] [Bug 443] spp primary takes up the complete hugepages
Date: Fri, 17 Apr 2020 08:25:14 +0000 [thread overview]
Message-ID: <bug-443-394-2IoMFrrSkL@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 #6 from Hideyuki Yamashita (yamashita.hideyuki@ntt-tx.co.jp) ---
Hello Vipin,
Thanks for your response.
Unfortunately I could not observe the issue using DPDK19.11+SPP19.11.
[Hugepage usage]
Before primary process invoke
$ cat /proc/meminfo | grep -i HugePages
AnonHugePages: 0 kB
ShmemHugePages: 0 kB
HugePages_Total: 16
HugePages_Free: 16
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 1048576 kB
During primary process invoke
$ cat /proc/meminfo | grep -i HugePages
AnonHugePages: 0 kB
ShmemHugePages: 0 kB
HugePages_Total: 16
HugePages_Free: 14
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 1048576 kB
It looks that only 2 pages are used per primary invokation.
[SPP primary startup parameters]
sudo ./src/primary/x86_64-native-linuxapp-gcc/spp_primary \
-l 1 \
-n 4 \
--socket-mem 512,512 \
--huge-dir /mnt/huge1G \
--proc-type primary \
-- \
-p 0x03 \
-n 10 \
-s 127.0.0.1:5555
[How to reserve hugepages]
/etc/default/grub
GRUB_CMDLINE_LINUX="DEBCONF_DEBUG=5 ksdevice=bootif default_hugepagesz=1G
hugepagesz=1G hugepages=16"
hugepages mount directory
/mnt/huge_1GB
sudo mount |grep huge
nodev on /mnt/huge1G type hugetlbfs (rw,relatime,pagesize=1024M)
Thanks,
Hideyuki
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-04-17 8:25 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 [this message]
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
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-2IoMFrrSkL@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).