From: Alexander Duyck <alexander.duyck@gmail.com>
To: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: sridhar.samudrala@intel.com, edumazet@google.com, davem@davemloft.net
Subject: [net-next PATCH 0/2] NAPI ID fixups related to busy polling
Date: Mon, 20 Mar 2017 14:48:41 -0700 [thread overview]
Message-ID: <20170320214643.13922.51284.stgit@localhost.localdomain> (raw)
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(-)
--
next reply other threads:[~2017-03-20 21:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 21:48 Alexander Duyck [this message]
2017-03-20 21:48 ` [net-next PATCH 1/2] net: Busy polling should ignore sender CPUs Alexander Duyck
2017-03-20 22:16 ` Eric Dumazet
2017-03-20 21:48 ` [net-next PATCH 2/2] tcp: Record Rx hash and NAPI ID in tcp_child_process Alexander Duyck
2017-03-20 22:06 ` Eric Dumazet
2017-03-22 18:26 ` [net-next PATCH 0/2] NAPI ID fixups related to busy polling David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170320214643.13922.51284.stgit@localhost.localdomain \
--to=alexander.duyck@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sridhar.samudrala@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).