Soft Patch Panel
 help / color / mirror / Atom feed
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:00:59 +0000	[thread overview]
Message-ID: <bug-443-394-Pc7CutRDOA@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-443-394@http.bugs.dpdk.org/>

https://bugs.dpdk.org/show_bug.cgi?id=443

masahiro nemoto (masahiro.nemoto.es@s1.ntt-tx.co.jp) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |masahiro.nemoto.es@s1.ntt-t
                   |                            |x.co.jp

--- Comment #10 from masahiro nemoto (masahiro.nemoto.es@s1.ntt-tx.co.jp) ---
Hello Vipin,

I tried to re-create the situation you mentioned in your reply.

Before the result I would like to confirm that you pointed out the follwoing
two points.
[Point1]
 Primary: ``` x86_64-native-linuxapp-gcc/spp_primary -l 1-5 -n 4
--socket-mem=100,0 --proc-type=primary -w 0000:08:00.1 -w 0000:08:00.2 -- -p
0x3 -n 10 -s 127.0.0.1:5555 ```

Even if --socket-mem option is specified when invoking primary process, it is
ignored.

[Point2]
By adding new EAL parameter named--socket-limit pamaeter, the situation
changes. 
Total amount of memroy allocation is limited by parameter which is specified
with --socket-limit parameter.

[Result1]
I confiremed Point1 can be re-created in my environment.
sudo ./spp_primary -l 1-2 -n 4 --socket-mem=100,100 --proc-type=primary
--huge-dir=/mnt/huge1G -- -p 0x3 -n 10 -s 127.0.0.1:5555

by invoking above parameter, 1gigabyte per socket are allocated.
As you mentioned parameter value of --socket-mem is IGNORED.

tx_h-yamashita@r740n15:~$ sudo numastat -p spp_

Per-node process memory usage (in MBs)
PID                           Node 0          Node 1           Total
-------------------  --------------- --------------- ---------------
38174 (sudo)                    0.69            6.93            7.61
38175 (spp_primary)          1039.67         1027.32         2067.00
38183 (sudo)                    0.54            6.95            7.48
-------------------  --------------- --------------- ---------------
Total                        1040.89         1041.20         2082.09

[Result2]
sudo ./spp_primary -l 1-2 -n 4 --socket-mem=100,100 --socket-limit=10,10
--proc-type=primary --huge-dir=/mnt/huge1G -- -p 0x3 -n 10 -s 127.0.0.1:5555

With --socket-limit pameter, the situation did NOT change.
Expectation: 10 Mbytes per sockets are allocated.
Result: 1000Mbytes per sockets are allocated.

tx_h-yamashita@r740n15:~$ sudo numastat -p spp_

Per-node process memory usage (in MBs)
PID                           Node 0          Node 1           Total
-------------------  --------------- --------------- ---------------
38187 (sudo)                    0.68            6.95            7.63
38188 (spp_primary)          1039.61         1027.14         2066.75
38198 (sudo)                    0.54            6.75            7.30
-------------------  --------------- --------------- ---------------
Total                        1040.84         1040.84         2081.68

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2020-04-23  2:01 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 [this message]
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-Pc7CutRDOA@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).