From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] pci: limit default numa node to used devices Date: Fri, 21 Jul 2017 19:29:46 +0300 Message-ID: <2122264.yEe44PShKC@xps> References: <20170721091119.15701-1-sergio.gonzalez.monroy@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, nic@opencloud.tech To: Sergio Gonzalez Monroy Return-path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id CFDE8271 for ; Fri, 21 Jul 2017 18:29:52 +0200 (CEST) In-Reply-To: <20170721091119.15701-1-sergio.gonzalez.monroy@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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 Applied with title below, thanks pci: move NUMA node check from scan to probe