From: email@example.com To: firstname.lastname@example.org Subject: [spp] [Bug 443] spp primary takes up the complete hugepages Date: Mon, 20 Jul 2020 01:12:52 +0000 Message-ID: <bug-443-394-ALLmGVCpMh@http.bugs.dpdk.org/> (raw) In-Reply-To: <email@example.com/> https://bugs.dpdk.org/show_bug.cgi?id=443 --- Comment #14 from Vipin Varghese (firstname.lastname@example.org) --- Hello Masahiro, thank you for taking time and trying to understand the details. Following is my answers shared below 1, memory management of DPDK [Answer] for all final decision and right setup please reach out to DPDK memory manamangent maintainer. I can only suggest what I know. Q1. If user specify enough memory with '--socket-mem'(e.g. 5Gbytes), then no need to think about '--socket-limit'. [Answer] this is not the right understanding, because `socket-limit` is the upper (maximum) limit. This is been explained in comment-1. 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' [Answer] yes this is good argument, but only valid if there are not more than 2 primary application. In use cases (SPP is being used mostly) which has VM and dockers. So if one intents to ensure SPP primary requires minimum 512MB use `--socket-mem` and to ensure that dynamic allocations in SPP does not cross over 2048MB use `--socket-limit` 4. But it depends on 'characteristic of DPDK application',right? [Answer]Yes, I have explained the use case scenario. But for SPP this is not the cazse. At least, SPP does NOT need additional memory in runtime (rather primary process allocate memory only during initialization). [Answer] I think this is incorrect understand, If SPP is only standalone application there are no Docker, VM or Pod which will not dynamically grow or resize then you are safe not using the same. In addition, adding many parameters may lead to 'confusion' or 'mistype' and needs much workload to update documents. [Answer] I find this is as very inconsistent argument because 'if the intention is not to confuse users with argument, SPP should be hiding or abstract all EAL arguments from end user which it is failing to do' Your advice is highly appreciated. What do you think? [Answer] I think you should take this up with `Hideyuki Yamashita` (maintainer) on the direction of discussion and fixes. Note: Would not you agree, for the confirmed issue if the direction of the fix is not clear 1. there should have been meeting invitee or brain storming invites for the same. 2. If the goal is not to confuse end user with option, the SPP should be abstracting or templating EAL arg with zero maintenance. Hope all these will be fixed soon. -- You are receiving this mail because: You are on the CC list for the bug.
next prev 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 2020-07-20 1:12 ` bugzilla [this message] 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-ALLmGVCpMh@http.bugs.dpdk.org/ \ --email@example.com \ --firstname.lastname@example.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 \ email@example.com 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