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 52757A00C2 for ; Thu, 23 Apr 2020 04:01:01 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 35F5F1D40D; Thu, 23 Apr 2020 04:01:01 +0200 (CEST) Received: from inbox.dpdk.org (xvm-172-178.dc0.ghst.net [95.142.172.178]) by dpdk.org (Postfix) with ESMTP id DF9DE1D40D for ; Thu, 23 Apr 2020 04:00:59 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id B7A86A00C3; Thu, 23 Apr 2020 04:00:59 +0200 (CEST) From: bugzilla@dpdk.org To: spp@dpdk.org Date: Thu, 23 Apr 2020 02:00:59 +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: masahiro.nemoto.es@s1.ntt-tx.co.jp 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: cc 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 masahiro nemoto (masahiro.nemoto.es@s1.ntt-tx.co.jp) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |masahiro.nemoto.es@s1.ntt-t | |x.co.jp --- Comment #10 from masahiro nemoto (masahiro.nemoto.es@s1.ntt-tx.co.jp) -= -- Hello Vipin, I tried to re-create the situation you mentioned in your reply. Before the result I would like to confirm that you pointed out the follwoing two points. [Point1] Primary: ``` x86_64-native-linuxapp-gcc/spp_primary -l 1-5 -n 4 --socket-mem=3D100,0 --proc-type=3Dprimary -w 0000:08:00.1 -w 0000:08:00.2 = -- -p 0x3 -n 10 -s 127.0.0.1:5555 ``` Even if --socket-mem option is specified when invoking primary process, it = is ignored. [Point2] By adding new EAL parameter named--socket-limit pamaeter, the situation changes.=20 Total amount of memroy allocation is limited by parameter which is specified with --socket-limit parameter. [Result1] I confiremed Point1 can be re-created in my environment. sudo ./spp_primary -l 1-2 -n 4 --socket-mem=3D100,100 --proc-type=3Dprimary --huge-dir=3D/mnt/huge1G -- -p 0x3 -n 10 -s 127.0.0.1:5555 by invoking above parameter, 1gigabyte per socket are allocated. As you mentioned parameter value of --socket-mem is IGNORED. tx_h-yamashita@r740n15:~$ sudo numastat -p spp_ Per-node process memory usage (in MBs) PID Node 0 Node 1 Total ------------------- --------------- --------------- --------------- 38174 (sudo) 0.69 6.93 7.61 38175 (spp_primary) 1039.67 1027.32 2067.00 38183 (sudo) 0.54 6.95 7.48 ------------------- --------------- --------------- --------------- Total 1040.89 1041.20 2082.09 [Result2] sudo ./spp_primary -l 1-2 -n 4 --socket-mem=3D100,100 --socket-limit=3D10,10 --proc-type=3Dprimary --huge-dir=3D/mnt/huge1G -- -p 0x3 -n 10 -s 127.0.0.1= :5555 With --socket-limit pameter, the situation did NOT change. Expectation: 10 Mbytes per sockets are allocated. Result: 1000Mbytes per sockets are allocated. tx_h-yamashita@r740n15:~$ sudo numastat -p spp_ Per-node process memory usage (in MBs) PID Node 0 Node 1 Total ------------------- --------------- --------------- --------------- 38187 (sudo) 0.68 6.95 7.63 38188 (spp_primary) 1039.61 1027.14 2066.75 38198 (sudo) 0.54 6.75 7.30 ------------------- --------------- --------------- --------------- Total 1040.84 1040.84 2081.68 --=20 You are receiving this mail because: You are on the CC list for the bug.=