Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752887AbdCQDGq (ORCPT ); Thu, 16 Mar 2017 23:06:46 -0400 Received: from mail-pf0-f171.google.com ([209.85.192.171]:33677 "EHLO mail-pf0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752379AbdCQDGo (ORCPT ); Thu, 16 Mar 2017 23:06:44 -0400 Message-ID: <1489719448.28631.279.camel@edumazet-glaptop3.roam.corp.google.com> Subject: Re: [net-next PATCH 1/5] net: Do not record sender_cpu as napi_id in socket receive paths From: Eric Dumazet To: Alexander Duyck Cc: Netdev , "linux-kernel@vger.kernel.org" , "Samudrala, Sridhar" , Eric Dumazet , David Miller Date: Thu, 16 Mar 2017 19:57:28 -0700 In-Reply-To: References: <20170316183142.15806.38824.stgit@localhost.localdomain> <20170316183238.15806.14293.stgit@localhost.localdomain> <1489701936.28631.249.camel@edumazet-glaptop3.roam.corp.google.com> <1489704618.28631.267.camel@edumazet-glaptop3.roam.corp.google.com> 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: 255 Lines: 8 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.