Re: [net-next PATCH 1/5] net: Do not record sender_cpu as napi_id in socket receive paths

Alexander Duyck
2017-03-17T02:59:28Z

On Thu, Mar 16, 2017 at 7:57 PM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
> On Thu, 2017-03-16 at 19:40 -0700, Alexander Duyck wrote:
>
>> What I probably can do is go through and replace all the spots where
>> we where checking for sk_napi_id being 0, and instead replace it with
>> a check against NR_CPUS.
>
> This seems a good idea.

Right. This is the path I am planning to go with. It will require
about the same amount of code change but replaces those checks. I
just have to make sure I catch all the spots where we were checking it
for 0 but that shouldn't be too difficult of an issue.