From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.9 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 63251C0650F for ; Mon, 5 Aug 2019 09:46:22 +0000 (UTC) Received: from dpdk.org (dpdk.org [92.243.14.124]) by mail.kernel.org (Postfix) with ESMTP id 9E52B20B1F for ; Mon, 5 Aug 2019 09:46:21 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=monjalon.net header.i=@monjalon.net header.b="IkQsOJbR"; dkim=pass (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="JEPfTbKS" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 9E52B20B1F Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=monjalon.net Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=dev-bounces@dpdk.org Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id C98F51BDFE; Mon, 5 Aug 2019 11:46:20 +0200 (CEST) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 7F0F31BDEE for ; Mon, 5 Aug 2019 11:46:19 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id A9D9C21B81; Mon, 5 Aug 2019 05:46:18 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Mon, 05 Aug 2019 05:46:18 -0400 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=lr21vzAGeXD4K8k1N6GDd3qfeMCvA3gZNo17jlXzNBU=; b=IkQsOJbR7L0H 8ATxTf4hLR6WXTO698MocNjBukgR37Hz+aTUDgEVPq/jcNt/5G1RHXy5C/uAqdDC aj+URCzNoGuqdh1k2A9+8dslRoASiaw5CMji8YiVn3b+3/z7o2k3oC6ma9cc6U6o lbLOeNjmZOxXCDUJ2oJ+QOnPJwzezQs= 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=fm3; bh=lr21vzAGeXD4K8k1N6GDd3qfeMCvA3gZNo17jlXzN BU=; b=JEPfTbKSqhf4f7zF8WjpW8q/wH9Hhp4xECL88KDXLm5PBFKDAvwNs8/Q2 xFAwSvqKdppTERQE73fa+wyzT3TeuOEdGUNVS9F+fNL2S/FdzDFEZD3ChjTIHyMd QD8epM9kA/KUT3yn4TBSRmB6EFEZryjmOf9bMnox+eC1EQMP+Bqq3gEt3MmWcacL NCj+LA0BSxmSfiL7fn39vKmHvSiKAxKIKjMEAOGaLv5675XIT23lrDKUf7VWyrUh EpjO9XePifstYMtj/AvgvZQe6y/T67Z0qTMhCkeK2U+dQAGgEgVYIjLJeEYgzZZs 6eFPLR3ZrSrXGvmVdG8t2CSDMRgsQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddruddtjedgvddtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukf hppeejjedrudefgedrvddtfedrudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhh ohhmrghssehmohhnjhgrlhhonhdrnhgvthenucevlhhushhtvghrufhiiigvpedt 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 CE29D8005A; Mon, 5 Aug 2019 05:46:17 -0400 (EDT) From: Thomas Monjalon To: dev@dpdk.org Cc: "Burakov, Anatoly" Date: Mon, 05 Aug 2019 11:46:16 +0200 Message-ID: <2593550.902iN1ELt8@xps> In-Reply-To: <0a1c656a-9197-2060-5a28-f0fc72265651@intel.com> References: <20190718093432.14092-1-thomas@monjalon.net> <20190730172153.29008-1-thomas@monjalon.net> <0a1c656a-9197-2060-5a28-f0fc72265651@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v3] eal: warn on legacy memory allocation requirement 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 31/07/2019 11:15, Burakov, Anatoly: > On 30-Jul-19 6:21 PM, Thomas Monjalon wrote: > > When using --no-huge mode, dynamic allocation is not supported. > > Because of this limitation, the option --legacy-mem is implied > > and -m may be needed to specify the amount of memory to allocate. > > Otherwise the default amount MEMSIZE_IF_NO_HUGE_PAGE will be allocated. > > > > The option --socket-mem can also be used with --legacy-mem > > when hugepages are supported. > > > > Signed-off-by: Thomas Monjalon > > Acked-by: Anatoly Burakov Applied