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

Eric Dumazet
2017-03-17T02:55:26Z

On Thu, 2017-03-16 at 19:40 -0700, Alexander Duyck wrote:

> I don't know. My concern here is about the cost of going through all
> that code just for something that we know shouldn't be valid. If
> nothing else I might update sk_can_busy_loop so that it doesn't try
> busy looping on a sk_napi_id that is NR_CPU or less.

But why would that be a win ?

if napi_by_id() returns NULL, we immediately give up, (goto out;)

So why should we add a code that will add something that will not be
useful for the vast majority of the cases where the ID is valid and we
need to do the hash look up ?

Is libc trying to avoid doing syscalls like close(-1) ?