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

[bugzilla at dpdk.org]

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

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

I found the related documents of memory management of DPDK as following.
https://software.intel.com/content/www/us/en/develop/articles/memory-in-dpdk-part-4-1811-and-beyond.html

Now I think I understand the meaning of '--socket-mem' and '--socket-limit'.
But at the same time, new questions pops up.
Can you answer those basic questions.

Q1.
If user specify enough memory with '--socket-mem'(e.g. 5Gbytes), then no need
to think
about '--socket-limit'.
(However this may risk the situation like following:
"Large memory pre-allocated but almost all memory not used, thus waste of
memory from
system perspective")

Q2.
'--socket-limit' specifies upper limit of memory usage regardless of
'--socket-mem' value.
Then what is the risk(e.g. performance) when user specify '--socket-limit'
without '--socket-mem'.

In general I understand that it is 'safe' to specify both parameters
rather than specifying only one of those.

But it depends on 'characteristic of DPDK application',right?
At least, SPP does NOT need additional memory in runtime
(rather primary process allocate memory only during initialization).

In addition, adding many parameters may lead to 'confusion' or 'mistype'
and needs much workload to update documents.

Your advice is highly appreciated.
What do you think?

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