Soft Patch Panel
 help / color / Atom feed
From: bugzilla@dpdk.org
To: spp@dpdk.org
Subject: [spp] [Bug 443] spp primary takes up the complete hugepages
Date: Fri, 10 Jul 2020 07:24:23 +0000
Message-ID: <bug-443-394-cjImewZjEy@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 #13 from masahiro nemoto (masahiro.nemoto.es@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.

  parent reply index

Thread overview: 24+ 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
2020-04-23  2:23 ` bugzilla
2020-04-28  4:06 ` bugzilla
2020-07-10  7:24 ` bugzilla [this message]
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

Reply instructions:

You may reply publically 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-cjImewZjEy@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

Soft Patch Panel

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/spp/0 spp/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 spp spp/ http://inbox.dpdk.org/spp \
		spp@dpdk.org
	public-inbox-index spp


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.spp


AGPL code for this site: git clone https://public-inbox.org/ public-inbox