From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <thomas@monjalon.net>
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com
[66.111.4.25]) by dpdk.org (Postfix) with ESMTP id CFDE8271
for <dev@dpdk.org>; Fri, 21 Jul 2017 18:29:52 +0200 (CEST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
by mailout.nyi.internal (Postfix) with ESMTP id 74FCC2087B;
Fri, 21 Jul 2017 12:29:52 -0400 (EDT)
Received: from frontend1 ([10.202.2.160])
by compute1.internal (MEProxy); Fri, 21 Jul 2017 12:29:52 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h=
cc:content-transfer-encoding:content-type:date:from:in-reply-to
:message-id:mime-version:references:subject:to:x-me-sender
:x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=L/BWB9ECfrD2FUi
vPqTUNTYfKzbF4KK1YNKhZccJWsQ=; b=Ik1Ehggd+KPi7tSowWwbAqQozjlTJrr
h57ufJlMyaToMnwBDP6f3qADfJJWSXQ3J9wYGbx4U8YjiwoaQstOErBcU0NVDHsY
0htfgB848dfksupDgJm6Hynnu2S/VLG8UNhRUL1E3/lysmuDL1EfshKaO1eDaZRO
J5CDerzHJDOk=
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-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s=
fm1; bh=L/BWB9ECfrD2FUivPqTUNTYfKzbF4KK1YNKhZccJWsQ=; b=el2yw0sh
c2jNV4K49jFtlFe5d4okAIiBrVT1YJBIEjqfTQSkCP13XjTnCZtgAOQUvnjlg52H
Ji2jUt3shtkJnZI91U0dJsv/Y+rs1qqk1x+YM4oRIJK2pRoSiR3bDutWU6MxY9u4
Vpx68RliIt/wfyjyQLe+ldWVeNfcSNXr7f8kGQWL+a8arImuT7mW71qzNlzFqJZR
o+Gj+9HrJGw+nEtKq2LIsI26zBbZAWOxjH0GHEQCWsakM7ZiHXu/bZXChd5164vg
BWcUH/+uWt0bcNaCxvsbVkozdVXTFJ/zG+qMvdNAMk5/pqtqUMg1VWrnrec6uUTe
aXwsiYfZbvilCg==
X-ME-Sender: <xms:ACxyWRFsl2QEvu751ILAdmcHftJ1JaUTW2tpK5qH1V1vPqMxE41OoQ>
X-Sasl-enc: VfFxKMmoxzjKYYfuWcRsQNwxTO4XQhIGKFDZ0EE2vEva 1500654591
Received: from xps.localnet (unknown [37.163.5.152])
by mail.messagingengine.com (Postfix) with ESMTPA id 964107E31F;
Fri, 21 Jul 2017 12:29:51 -0400 (EDT)
From: Thomas Monjalon <thomas@monjalon.net>
To: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
Cc: dev@dpdk.org, nic@opencloud.tech
Date: Fri, 21 Jul 2017 19:29:46 +0300
Message-ID: <2122264.yEe44PShKC@xps>
In-Reply-To: <20170721091119.15701-1-sergio.gonzalez.monroy@intel.com>
References: <20170721091119.15701-1-sergio.gonzalez.monroy@intel.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [dpdk-dev] [PATCH] pci: limit default numa node to used devices
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
<mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
<mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2017 16:29:53 -0000
21/07/2017 12:11, Sergio Gonzalez Monroy:
> Commit 8a04cb612589 ("pci: set default numa node for broken systems")
> added logic to default to NUMA node 0 when sysfs numa_node information
> was wrong or not available.
>
> Unfortunately there are many devices with wrong NUMA node information
> that DPDK does not care about but still show warnings for them.
>
> Instead, only check for invalid NUMA node information for devices
> managed by the DPDK.
>
> Signed-off-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
Applied with title below, thanks
pci: move NUMA node check from scan to probe