Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1607989
| From | Eric Dumazet <eric.dumazet@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [net-next PATCH v2 8/8] net: Introduce SO_INCOMING_NAPI_ID |
| Date | 2017-03-23 23:30 +0100 |
| Message-ID | <tojp0-pl-13@gated-at.bofh.it> (permalink) |
| References | <toiCB-8g8-3@gated-at.bofh.it> <toiCC-8g8-29@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Thu, 2017-03-23 at 14:38 -0700, Alexander Duyck wrote: > From: Sridhar Samudrala <sridhar.samudrala@intel.com> > > This socket option returns the NAPI ID associated with the queue on which > the last frame is received. This information can be used by the apps to > split the incoming flows among the threads based on the Rx queue on which > they are received. > > If the NAPI ID actually represents a sender_cpu then the value is ignored > and 0 is returned. Acked-by: Eric Dumazet <edumazet@google.com>
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[net-next PATCH v2 8/8] net: Introduce SO_INCOMING_NAPI_ID Alexander Duyck <alexander.duyck@gmail.com> - 2017-03-23 22:40 +0100
Re: [net-next PATCH v2 8/8] net: Introduce SO_INCOMING_NAPI_ID Eric Dumazet <eric.dumazet@gmail.com> - 2017-03-23 23:30 +0100
Re: [net-next PATCH v2 8/8] net: Introduce SO_INCOMING_NAPI_ID Andy Lutomirski <luto@kernel.org> - 2017-03-23 23:50 +0100
Re: [net-next PATCH v2 8/8] net: Introduce SO_INCOMING_NAPI_ID Alexander Duyck <alexander.duyck@gmail.com> - 2017-03-24 02:00 +0100
Re: [net-next PATCH v2 8/8] net: Introduce SO_INCOMING_NAPI_ID Andy Lutomirski <luto@kernel.org> - 2017-03-24 05:50 +0100
Re: [net-next PATCH v2 8/8] net: Introduce SO_INCOMING_NAPI_ID Eric Dumazet <edumazet@google.com> - 2017-03-24 06:10 +0100
csiph-web