Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932100AbdCTVsw (ORCPT ); Mon, 20 Mar 2017 17:48:52 -0400 Received: from mail-pg0-f44.google.com ([74.125.83.44]:33487 "EHLO mail-pg0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755825AbdCTVst (ORCPT ); Mon, 20 Mar 2017 17:48:49 -0400 Subject: [net-next PATCH 0/2] NAPI ID fixups related to busy polling From: Alexander Duyck To: netdev@vger.kernel.org, linux-kernel@vger.kernel.org Cc: sridhar.samudrala@intel.com, edumazet@google.com, davem@davemloft.net Date: Mon, 20 Mar 2017 14:48:41 -0700 Message-ID: <20170320214643.13922.51284.stgit@localhost.localdomain> User-Agent: StGit/0.17.1-dirty MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 794 Lines: 22 These two patches are a couple of minor clean-ups related to busy polling. The first one addresses the fact that we were trying to busy poll on sender_cpu values instead of true NAPI IDs. The second addresses the fact that there were a few paths where TCP sockets were being instanciated based on a received patcket, but not recording the hash or NAPI ID of the packet that was used to instanciate them. --- Alexander Duyck (2): net: Busy polling should ignore sender CPUs tcp: Record Rx hash and NAPI ID in tcp_child_process include/net/busy_poll.h | 11 +++++++++-- net/core/dev.c | 6 +++--- net/ipv4/tcp_ipv4.c | 2 -- net/ipv4/tcp_minisocks.c | 5 +++++ net/ipv6/tcp_ipv6.c | 2 -- 5 files changed, 17 insertions(+), 9 deletions(-) --