Re: [dpdk-dev] [PATCH] pci: limit default numa node to used devices

2017-07-21 Thread Thomas Monjalon
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

Re: [dpdk-dev] [PATCH] pci: limit default numa node to used devices

2017-07-21 Thread Thomas Monjalon
21/07/2017 18:47, Sergio Gonzalez Monroy: > On 21/07/2017 16:37, Thomas Monjalon wrote: > > 21/07/2017 18:03, Sergio Gonzalez Monroy: > >> On 21/07/2017 15:53, Thomas Monjalon wrote: > >>> The title and the text below should explain that you move > >>> the warning log from scan to probe, thanks to

Re: [dpdk-dev] [PATCH] pci: limit default numa node to used devices

2017-07-21 Thread Sergio Gonzalez Monroy
On 21/07/2017 16:37, Thomas Monjalon wrote: 21/07/2017 18:03, Sergio Gonzalez Monroy: On 21/07/2017 15:53, Thomas Monjalon wrote: The title and the text below should explain that you move the warning log from scan to probe, thanks to a temporary negative value. I thought that saying that I onl

Re: [dpdk-dev] [PATCH] pci: limit default numa node to used devices

2017-07-21 Thread Thomas Monjalon
21/07/2017 18:03, Sergio Gonzalez Monroy: > On 21/07/2017 15:53, Thomas Monjalon wrote: > > The title and the text below should explain that you move > > the warning log from scan to probe, thanks to a temporary > > negative value. > > I thought that saying that I only check for devices managed by

Re: [dpdk-dev] [PATCH] pci: limit default numa node to used devices

2017-07-21 Thread Sergio Gonzalez Monroy
On 21/07/2017 15:53, Thomas Monjalon wrote: The title and the text below should explain that you move the warning log from scan to probe, thanks to a temporary negative value. I thought that saying that I only check for devices managed by dpdk explains the purpose, and the patch itself shows

Re: [dpdk-dev] [PATCH] pci: limit default numa node to used devices

2017-07-21 Thread Thomas Monjalon
The title and the text below should explain that you move the warning log from scan to probe, thanks to a temporary negative value. 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 n

[dpdk-dev] [PATCH] pci: limit default numa node to used devices

2017-07-21 Thread 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 t