From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id E8FF625D9; Wed, 23 Jan 2019 23:03:10 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 59D0120336; Wed, 23 Jan 2019 17:03:10 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 23 Jan 2019 17:03:10 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=5vj5CIweVz70JV2ijs+NVtqnGzQUq8UUpxNTY/N1bLg=; b=GTlHPBtpNMej lDwfIr/xxy/NuvElTuYanWGWGYL362nb7YpLm5fHd44up1hvFbs3IugQAFe5ECUv FznhxiF0OuIHbL9CQw6IohpYD/Jm8oce5y0+2srw8yJgsveKZPMcqIuQlXzQBQsh 2Z1JszzMjOnZdPea4EqeuMCATrJ3WZU= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=5vj5CIweVz70JV2ijs+NVtqnGzQUq8UUpxNTY/N1b Lg=; b=QORoWR+nBE5kkkhitYHbUU/2X/7UhXfkF9KDhFKv4HDKd+3C0VjUOJopI mB0egMosCak7Sbv/PrfAMn8nhiUZvWXf9hddId5/galLIWJXxdeav9xCYCFJlTSS 5gO9rNI66vqqMoLQOuj3P1y1/0Dr/9b5njk9yH6ixzpCEGj7WERpVIjWv9Bu+glu ug1ZrwcWxqSuoH2PkG3EFxkmNhqJEclMV5XF+VtppgfmX6g4kPoigEoaSzFLlbVJ Oz2epFI1XUApx3CmDEY60tvjBFA9zZ33mMgKCgwEziZq/D5TTYbUiieiZddtjFk6 xWiGn8LRTYvw19auCsu6SbjwebuDQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledriedtgdduheekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfquhhtnecuuegrihhlohhuthemucef tddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefhvffufffkjg hfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghsucfoohhnjhgrlhhonhcu oehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkphepjeejrddufeegrddvtd efrddukeegnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghl ohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id C5BDA10086; Wed, 23 Jan 2019 17:03:08 -0500 (EST) From: Thomas Monjalon To: Ilya Maximets Cc: stable@dpdk.org, "Burakov, Anatoly" , dev@dpdk.org Date: Wed, 23 Jan 2019 23:03:07 +0100 Message-ID: <4900677.582JXVQWH1@xps> In-Reply-To: <1a3eea71-1b1a-7589-48fa-71a23ee1e0a2@intel.com> References: <20190122162714.9144-1-i.maximets@samsung.com> <1a3eea71-1b1a-7589-48fa-71a23ee1e0a2@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] eal: fix parsing zero socket memory and limits X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jan 2019 22:03:11 -0000 23/01/2019 11:15, Burakov, Anatoly: > On 22-Jan-19 4:27 PM, Ilya Maximets wrote: > > Modern memory mode allowes to not reserve any memory by the > > '--socket-mem' option. i.e. it could be possible to specify > > zero preallocated memory like '--socket-mem 0'. > > Also, it should be possible to configure unlimited memory > > allocations by '--socket-limit 0'. > > > > Both cases are impossible now and blocks starting the DPDK > > application: > > > > ./dpdk-app --socket-limit 0 <...> > > EAL: invalid parameters for --socket-limit > > EAL: Invalid 'command line' arguments. > > Unable to initialize DPDK: Invalid argument > > > > Fixes: 6b42f75632f0 ("eal: enable non-legacy memory mode") > > Cc: stable@dpdk.org > > > > Signed-off-by: Ilya Maximets > > --- > > That's kind of an odd parameter to pass, as it is assumed that if you > don't need any limitations or preallocated memory, you don't specify > these flags in the first place, but OK :) > > Acked-by: Anatoly Burakov Applied, thanks