Re: [net-next PATCH 3/5] net: Introduce SO_INCOMING_NAPI_ID

On Thu, 2017-03-16 at 11:32 -0700, Alexander Duyck wrote:

 
+	case SO_INCOMING_NAPI_ID:
+		v.val = sk->sk_napi_id;
+		break;

I guess that here you should filter invalid values.

(So that you no longer need the first patch in this series)

Also, it looks like eBPF will need to get access to skb->napi_id for
efficient SO_REUSEPORT support ?

Thanks.