From: Paolo Abeni <pabeni@redhat.com>
To: netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
Edward Cree <ecree@solarflare.com>
Subject: [PATCH net-next 0/2] net: introduce and use route hint
Date: Sat, 16 Nov 2019 10:14:49 +0100 [thread overview]
Message-ID: <cover.1573893340.git.pabeni@redhat.com> (raw)
This series leverages the listification infrastructure to avoid
unnecessary route lookup on ingress packets. In absence of policy routing,
packets with equal daddr will usually land on the same dst.
When processing packet bursts (lists) we can easily reference the previous
dst entry. When we hit the 'same destination' condition we can avoid the
route lookup, coping the already available dst.
Detailed performance numbers are available in the individual commit messages.
Paolo Abeni (2):
ipv6: introduce and uses route look hints for list input
ipv4: use dst hint for ipv4 list receive
include/net/route.h | 11 +++++++++++
net/ipv4/ip_input.c | 29 ++++++++++++++++++++++++-----
net/ipv4/route.c | 38 ++++++++++++++++++++++++++++++++++++++
net/ipv6/ip6_input.c | 30 ++++++++++++++++++++++++++----
4 files changed, 99 insertions(+), 9 deletions(-)
--
2.21.0
next reply other threads:[~2019-11-16 9:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-16 9:14 Paolo Abeni [this message]
2019-11-16 9:14 ` [PATCH net-next 1/2] ipv6: introduce and uses route look hints for list input Paolo Abeni
2019-11-16 11:04 ` kbuild test robot
2019-11-17 11:46 ` kbuild test robot
2019-11-16 9:14 ` [PATCH net-next 2/2] ipv4: use dst hint for ipv4 list receive Paolo Abeni
2019-11-16 10:56 ` kbuild test robot
2019-11-17 8:58 ` kbuild test robot
2019-11-18 16:15 ` Edward Cree
2019-11-18 16:44 ` Paolo Abeni
2019-11-18 17:14 ` Paolo Abeni
2019-11-16 20:09 ` [PATCH net-next 0/2] net: introduce and use route hint David Miller
2019-11-18 8:12 ` Paolo Abeni
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=cover.1573893340.git.pabeni@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=ecree@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=willemdebruijn.kernel@gmail.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).