Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754639AbdCPW64 (ORCPT ); Thu, 16 Mar 2017 18:58:56 -0400 Received: from mail-pg0-f67.google.com ([74.125.83.67]:33464 "EHLO mail-pg0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752680AbdCPW6v (ORCPT ); Thu, 16 Mar 2017 18:58:51 -0400 Message-ID: <1489703227.28631.253.camel@edumazet-glaptop3.roam.corp.google.com> Subject: Re: [net-next PATCH 3/5] net: Introduce SO_INCOMING_NAPI_ID From: Eric Dumazet To: Alexander Duyck Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org, sridhar.samudrala@intel.com, edumazet@google.com, davem@davemloft.net Date: Thu, 16 Mar 2017 15:27:07 -0700 In-Reply-To: <20170316183250.15806.59426.stgit@localhost.localdomain> References: <20170316183142.15806.38824.stgit@localhost.localdomain> <20170316183250.15806.59426.stgit@localhost.localdomain> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4-0ubuntu2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 361 Lines: 16 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.