examples/flow_classify: fix NUMA check of port and core
According to the comments and logging, the author just hope user to use the core and device which are in the same numa node for optimal performance. If not, A warning gives out. For example in flow_classify: ./build/flow_classify -a 0000:7d:00.1 -l 93 Here: 0000:7d:00.1 is on numa node 0. core 93 is on numa node 3. The two are not in same numa node, but no warning gives out in old codes when device is on node 0. This patch includes the node 0 in the check. Fixes: bab16ddaf2c1 ("examples/flow_classify: add sample application") Cc: stable@dpdk.org Signed-off-by: Min Hu (Connor) <humin29@huawei.com> Tested-by: Bernard Iremonger <bernard.iremonger@intel.com> Acked-by: Bernard Iremonger <bernard.iremonger@intel.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
This commit is contained in:
parent
7861009f7b
commit
78a5545ef9
@ -284,7 +284,7 @@ lcore_main(struct flow_classifier *cls_app)
|
||||
* for best performance.
|
||||
*/
|
||||
RTE_ETH_FOREACH_DEV(port)
|
||||
if (rte_eth_dev_socket_id(port) > 0 &&
|
||||
if (rte_eth_dev_socket_id(port) >= 0 &&
|
||||
rte_eth_dev_socket_id(port) != (int)rte_socket_id()) {
|
||||
printf("\n\n");
|
||||
printf("WARNING: port %u is on remote NUMA node\n",
|
||||
|
Loading…
x
Reference in New Issue
Block a user