From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 8045BA05D3 for ; Sat, 30 Mar 2019 00:27:32 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 3A09837A2; Sat, 30 Mar 2019 00:27:32 +0100 (CET) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 435862965; Sat, 30 Mar 2019 00:27:27 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id D57F321E5A; Fri, 29 Mar 2019 19:27:26 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 29 Mar 2019 19:27:26 -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=kwfEWe/AC4vbh7acvpnGFQKMKeEEQjzH7tnrq7iS+p4=; b=Tmt1yf40Wc2m 9YOpGZ8hID1NP8YarzAm3lK0t6d/47HtPLmBjlX7zTGRLC+A490qyp9JH1kQc7bJ Ka3G6Mw6FhxY0L3Lr8XDlso/mlHGl07TSe7rHsNE3WxJol/PtRG665frAdEnOmie Pi3deQSwqtzu9r0sThO25ZD0LnP70sw= 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=fm2; bh=kwfEWe/AC4vbh7acvpnGFQKMKeEEQjzH7tnrq7iS+ p4=; b=nk8MbzpidGNh7Dhy6JIVMgYVUnhQomnnVHlh36jQmUK+bt9qdTr0aQciG QmIglj1VvY2JJ6dTaXgXG356LQLqNRn6Vx1rk3BDuJBhAe4WXlNdIVw3TdseCW4e mvuL0+IXkUqUlDkPIQzpmpmh31NB9tanq6ixVa4BaR7vzSoQCre5fr2MoRZUI2mH MWrZDRmkOhucr1ePPgYDYZqOxXH1sZke46LpatXmHrn+OlMILEXySiRj+Mw0swxu lU3cECKkYiApgTMaxNzjxBqjRIPZ0UbGJ6XFyOdonOBQEmbXqm5JD1H6xEXp2Wvb r2zn3wc9vrKCvYom9VFbUlTSUyuPA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrkeekgddutdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkph epjeejrddufeegrddvtdefrddukeegnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhho mhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd 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 9EEB8E4666; Fri, 29 Mar 2019 19:27:25 -0400 (EDT) From: Thomas Monjalon To: Anatoly Burakov Cc: stable@dpdk.org, dev@dpdk.org Date: Sat, 30 Mar 2019 00:27:24 +0100 Message-ID: <1845933.y3QeW7bodN@xps> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-stable] [PATCH v4] mem: warn user when running without NUMA support X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Sender: "stable" 29/03/2019 15:01, Anatoly Burakov: > Running in non-legacy mode on a NUMA-enabled system without libnuma > is unsupported, so explicitly print out a warning when trying to > do so. > > Running in legacy mode without libnuma is still supported whether or > not we are running with libnuma support enabled, so also fix init to > allow that scenario. > > Cc: stable@dpdk.org > > Signed-off-by: Anatoly Burakov Applied, thanks