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

[bugzilla@dpdk.org]

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

--- Comment #22 from Vipin Varghese (vipin.varghese@intel.com) ---

I understand that this ticket is related with "hugepage usage" as ticket title
tells.
[VV] thanks for agreeing

I understand that hugepage usage does NOT increase regardless of number of
secondary process.
[VV] thanks for confirming the same.

The following is the result
- hugepage in system is 16G
[VV] are you stating the SPP requires 16GB of memory as hugepages to work. Only
place mentioning about memory is
`https://doc.dpdk.org/spp/setup/getting_started.html#setup`. 

problem-1: But here it is contracting with `1GB is 8` and with `2MB is 1024`.
this is the first concern there is no minimum requirement.

problem-2: Without setting lower limit via `--socket-mem` and upper limit
`--socket-limit`, other DPDK applciations can consume the huge pages leading to
exhgaustation of pages.

probelm-3: Earlier interactions from `Masahiro Nemoto` and `Hideyuki Yamashita`
did not see change in huge page or allocation of memory from secodnary from the
day ticket being opened (2020-04-06 08:25:15). But I am happy to udnerstand
that we all agree starting secondary leads to 1GB consumption.

In my humble opinion right actions for better use of SPP and SPP community
would be to

a. confirm this has been present in earlier and current releases.

b. update documentation in minimum memory requirement for running priamry and
secondaries.

c. update documentation minimum memory utilziation for launching secodnaries is
1GB each.

d. edit the start or EAL-ARGS to reflect the based on user configuration (1GB
for priamry + 1GB * n secondaries)

e. updating eal-args of spp_primary with socket-limit to prevent using more
than `1GB for priamry + 1GB * n secondaries.

Please feel free if you have difference in opinion.

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