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

From	Alexander Duyck <alexander.duyck@gmail.com>
Newsgroups	linux.kernel
Subject	Re: [net-next PATCH 1/5] net: Do not record sender_cpu as napi_id in socket receive paths
Date	2017-03-17 04:00 +0100
Message-ID	<tlQhs-7K9-5@gated-at.bofh.it> (permalink)
References	(2 earlier) <tlLKN-4LF-5@gated-at.bofh.it> <tlMnw-51X-17@gated-at.bofh.it> <tlMxb-56x-5@gated-at.bofh.it> <tlQ7L-7Ds-1@gated-at.bofh.it> <tlQhs-7K9-7@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

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.

Thread

[net-next PATCH 0/5] Add busy poll support for epoll under certain  circumstances Alexander Duyck <alexander.duyck@gmail.com> - 2017-03-16 19:40 +0100
  [net-next PATCH 1/5] net: Do not record sender_cpu as napi_id in  socket receive paths Alexander Duyck <alexander.duyck@gmail.com> - 2017-03-16 19:40 +0100
    Re: [net-next PATCH 1/5] net: Do not record sender_cpu as napi_id  in socket receive paths Eric Dumazet <eric.dumazet@gmail.com> - 2017-03-16 23:10 +0100
      Re: [net-next PATCH 1/5] net: Do not record sender_cpu as napi_id in  socket receive paths Alexander Duyck <alexander.duyck@gmail.com> - 2017-03-16 23:50 +0100
        Re: [net-next PATCH 1/5] net: Do not record sender_cpu as napi_id  in socket receive paths Eric Dumazet <eric.dumazet@gmail.com> - 2017-03-17 00:00 +0100
          Re: [net-next PATCH 1/5] net: Do not record sender_cpu as napi_id in  socket receive paths Alexander Duyck <alexander.duyck@gmail.com> - 2017-03-17 03:50 +0100
            Re: [net-next PATCH 1/5] net: Do not record sender_cpu as napi_id  in socket receive paths Eric Dumazet <eric.dumazet@gmail.com> - 2017-03-17 04:00 +0100
            Re: [net-next PATCH 1/5] net: Do not record sender_cpu as napi_id in  socket receive paths Alexander Duyck <alexander.duyck@gmail.com> - 2017-03-17 04:00 +0100
            Re: [net-next PATCH 1/5] net: Do not record sender_cpu as napi_id  in socket receive paths Eric Dumazet <eric.dumazet@gmail.com> - 2017-03-17 04:10 +0100
      Re: [net-next PATCH 1/5] net: Do not record sender_cpu as napi_id  in socket receive paths "Samudrala, Sridhar" <sridhar.samudrala@intel.com> - 2017-03-16 23:50 +0100
  [net-next PATCH 2/5] net: Call sk_mark_napi_id() in the ACK receive  path Alexander Duyck <alexander.duyck@gmail.com> - 2017-03-16 19:40 +0100
    Re: [net-next PATCH 2/5] net: Call sk_mark_napi_id() in the ACK  receive path Eric Dumazet <eric.dumazet@gmail.com> - 2017-03-16 23:10 +0100
      Re: [net-next PATCH 2/5] net: Call sk_mark_napi_id() in the ACK  receive path Alexander Duyck <alexander.duyck@gmail.com> - 2017-03-16 23:40 +0100
  [net-next PATCH 3/5] net: Introduce SO_INCOMING_NAPI_ID Alexander Duyck <alexander.duyck@gmail.com> - 2017-03-16 19:40 +0100
    Re: [net-next PATCH 3/5] net: Introduce SO_INCOMING_NAPI_ID Eric Dumazet <eric.dumazet@gmail.com> - 2017-03-17 00:00 +0100
  Re: [net-next PATCH 0/5] Add busy poll support for epoll under  certain circumstances Michael Kerrisk <mtk.manpages@gmail.com> - 2017-03-18 12:50 +0100

csiph-web