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 0D6BFA00C2 for ; Thu, 23 Apr 2020 04:23:50 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id E006A1D408; Thu, 23 Apr 2020 04:23:49 +0200 (CEST) Received: from inbox.dpdk.org (xvm-172-178.dc0.ghst.net [95.142.172.178]) by dpdk.org (Postfix) with ESMTP id 850891D408 for ; Thu, 23 Apr 2020 04:23:48 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id 58EC9A00C4; Thu, 23 Apr 2020 04:23:48 +0200 (CEST) From: bugzilla@dpdk.org To: spp@dpdk.org Date: Thu, 23 Apr 2020 02:23:48 +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: UNCONFIRMED 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 #11 from Vipin Varghese (vipin.varghese@intel.com) --- Hi Hideyuki, thanks for your updates. Summarizing your findings 1. The issue can be reproduced. 2. The parameter ```--socket-mem=3D100,100 --socket-limit=3D10,10 ``` did n= ot make difference for you. My Answers 1. you can move the status of the bug to `confirmed`. 2. The parameter usage ```--socket-mem=3D100,100 --socket-limit=3D10,10``` = is not correct. Let me explain: a. option ```socket-mem`` defines the minimum amount memory to be used form huge page. b. option ```socket-limit``` defines the max limit the memory to be used fr= om huge page. Hence if you want to use memory from=20 1. NUMA-0, it should be ```--socket-limit=3D100,1 --socket-mem=3D1024,1``` 2. NUMA-1, it should be ```--socket-limit=3D1,100 --socket-mem=3D1,1024``` 3. NUMA-0 and NUMA-1, it should be ```--socket-limit=3D100,100 --socket-mem=3D1024,1024``` This prevents primary or secondaries hijacking huge pages beyond ```socket-limit``` --=20 You are receiving this mail because: You are on the CC list for the bug.=