From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id C9207A0540; Mon, 20 Jul 2020 03:12:54 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 8AEB02BC8; Mon, 20 Jul 2020 03:12:54 +0200 (CEST) Received: from inbox.dpdk.org (xvm-172-178.dc0.ghst.net [95.142.172.178]) by dpdk.org (Postfix) with ESMTP id A685D2BC8 for ; Mon, 20 Jul 2020 03:12:53 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id 73F8FA0548; Mon, 20 Jul 2020 03:12:53 +0200 (CEST) From: bugzilla@dpdk.org To: spp@dpdk.org Date: Mon, 20 Jul 2020 01:12:52 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: SPP X-Bugzilla-Component: main X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: vipin.varghese@intel.com X-Bugzilla-Status: CONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: High X-Bugzilla-Assigned-To: yasufum.o@gmail.com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 Subject: [spp] [Bug 443] spp primary takes up the complete hugepages X-BeenThere: spp@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Soft Patch Panel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: spp-bounces@dpdk.org Sender: "spp" https://bugs.dpdk.org/show_bug.cgi?id=3D443 --- Comment #14 from Vipin Varghese (vipin.varghese@intel.com) --- Hello Masahiro, thank you for taking time and trying to understand the details. Following i= s my answers shared below 1, memory management of DPDK [Answer] for all final decision and right setup please reach out to DPDK me= mory 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 spe= cify '--socket-limit' without '--socket-mem' [Answer] yes this is good argument, but only valid if there are not more th= an 2 primary application. In use cases (SPP is being used mostly) which has VM a= nd 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?=20 [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 inten= tion 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` (maintai= ner) on the direction of discussion and fixes.=20 Note: Would not you agree, for the confirmed issue if the direction of the = fix is not clear=20 1. there should have been meeting invitee or brain storming invites for the same.=20 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. --=20 You are receiving this mail because: You are on the CC list for the bug.=