[spp] [Bug 443] spp primary takes up the complete hugepages

[bugzilla at dpdk.org]

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

--- Comment #16 from Vipin Varghese (vipin.varghese at intel.com) ---
Hi Hideyuku,

Please find the information which show cases how hugepage is dynamically
consumed in SPP

```
Vipin Varghese 2020-04-19 08:50:36 CEST
Hi Hideyuki,

I am not sure, whether it's the download or the missing information in the
documentation. 

URL: https://doc.dpdk.org/spp/setup/getting_started.html#setup
DPDK version: mainline from git
SPP version: spp-19.11.zip


Observation: Primary is resource allocator (huge page), without secondary it
consumes 1Gb (1 page from the hugepage). Starting of secondary without
```socket-limit``` it is free to consume next huge page.

Memory Usage:
# numastat -p spp_

Per-node process memory usage (in MBs)
PID                           Node 0          Node 1           Total
-------------------  --------------- --------------- ---------------
15191 (gdb)                    54.12            3.23           57.35
15201 (spp_primary)          1040.76            2.12         1042.88
15208 (spp_nfv)              1039.82            2.29         1042.11
-------------------  --------------- --------------- ---------------
Total                        2134.70            7.64         2142.34
```

Please note this is confirmed and shared on `2020-04-19 08:50:36` in the same
ticket. 

`SPP rarely allocates memory in dynamically and thus SPP document guides users
to allocate enough memory by using "--socket-mem" option`. 
[request] Can you please confirm you are not seeing this.

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