I asked about this many months ago and was informed that "-1" is a "standard error value" that I should expect from these APIs when NUMA is not present. Now we're saying I have to change my code again to handle a zero value?
Also not sure how to tell the difference between no NUMA, something running on socket zero, and something with multiple sockets. Seems like we need a bit of thought about how the NUMA APIs should behave overall. Matthew. On Fri, Jul 31, 2015 at 09:36:12AM +0800, Cunming Liang wrote: > The patch sets zero as the default value of pci device numa_node > if the socket could not be determined. > It provides the same default value as FreeBSD which has no NUMA support, > and makes the return value of rte_eth_dev_socket_id() be consistent > with the API description. > > Signed-off-by: Cunming Liang <cunming.liang at intel.com>
