Re: [dpdk-dev] [PATCH v3 0/3] fix check of port and core

From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Min Hu (Connor)" <humin29@huawei.com>, dev@dpdk.org
Cc: bernard.iremonger@intel.com, thomas@monjalon.net
Subject: Re: [dpdk-dev] [PATCH v3 0/3] fix check of port and core
Date: Wed, 12 May 2021 17:52:42 +0100	[thread overview]
Message-ID: <8c549935-875f-ff70-3e1f-5d56503059b7@intel.com> (raw)
In-Reply-To: <1619657448-57567-1-git-send-email-humin29@huawei.com>

On 4/29/2021 1:50 AM, Min Hu (Connor) wrote:
> Currently, some examples check that the port is on the same NUMA
> node as the polling thread for best performance. The method is
> to compare the socket id of port and that of current core. If the
> result is different, warning info will be given.
> 
> But it ignores the port which is from numa node 0, that is, no
> warning info will be given if the port is from numa node 0, and
> this set of patches will fix it.
> ---
> v3:
> * change "-w" to "-a".
> 
> v2:
> * add more commit info.
> 
> Min Hu (Connor) (3):
>   examples/flow_classify: fix check of port and core
>   examples/l2fwd-cat: fix check of port and core
>   examples/skeleton: fix check of port and core
> 

For series,
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>

Only I am not sure if it is confusing to mention from 'flow_classify' in the
commit log of 'l2fwd-cat' or 'skeleton' patches.