From: Edward Cree <ecree@solarflare.com>
To: Paolo Abeni <pabeni@redhat.com>, <netdev@vger.kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
David Ahern <dsahern@gmail.com>,
"Eric Dumazet" <eric.dumazet@gmail.com>
Subject: Re: [PATCH net-next v4 0/5] net: introduce and use route hint
Date: Wed, 20 Nov 2019 16:54:47 +0000 [thread overview]
Message-ID: <7b5fe6ee-4fa2-a6bd-890c-160fff3ec74d@solarflare.com> (raw)
In-Reply-To: <cover.1574252982.git.pabeni@redhat.com>
On 20/11/2019 12:47, Paolo Abeni wrote:
> This series leverages the listification infrastructure to avoid
> unnecessary route lookup on ingress packets. In absence of custom rules,
> 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.
I wonder if you could use static keys for the fib*_has_custom_rules()
and if that would gain you any extra speed?
Other than that,
Acked-by: Edward Cree <ecree@solarflare.com>
for the series.
>
> v3 -> v4:
> - move helpers to their own patches (Eric D.)
> - enable hints for SUBTREE builds (David A.)
> - re-enable hints for ipv4 forward (David A.)
>
> v2 -> v3:
> - use fib*_has_custom_rules() helpers (David A.)
> - add ip*_extract_route_hint() helper (Edward C.)
> - use prev skb as hint instead of copying data (Willem )
>
> v1 -> v2:
> - fix build issue with !CONFIG_IP*_MULTIPLE_TABLES
> - fix potential race in ip6_list_rcv_finish()
>
> Paolo Abeni (5):
> ipv6: add fib6_has_custom_rules() helper
> ipv6: keep track of routes using src
> ipv6: introduce and uses route look hints for list input.
> ipv4: move fib4_has_custom_rules() helper to public header
> ipv4: use dst hint for ipv4 list receive
>
> include/net/ip6_fib.h | 39 +++++++++++++++++++++++++++++++++++++
> include/net/ip_fib.h | 10 ++++++++++
> include/net/netns/ipv6.h | 3 +++
> include/net/route.h | 4 ++++
> net/ipv4/fib_frontend.c | 10 ----------
> net/ipv4/ip_input.c | 35 +++++++++++++++++++++++++++++----
> net/ipv4/route.c | 42 ++++++++++++++++++++++++++++++++++++++++
> net/ipv6/ip6_fib.c | 4 ++++
> net/ipv6/ip6_input.c | 26 +++++++++++++++++++++++--
> net/ipv6/route.c | 3 +++
> 10 files changed, 160 insertions(+), 16 deletions(-)
>
next prev parent reply other threads:[~2019-11-20 16:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 12:47 [PATCH net-next v4 0/5] net: introduce and use route hint Paolo Abeni
2019-11-20 12:47 ` [PATCH net-next v4 1/5] ipv6: add fib6_has_custom_rules() helper Paolo Abeni
2019-11-21 20:07 ` David Ahern
2019-11-20 12:47 ` [PATCH net-next v4 2/5] ipv6: keep track of routes using src Paolo Abeni
2019-11-21 20:09 ` David Ahern
2019-11-20 12:47 ` [PATCH net-next v4 3/5] ipv6: introduce and uses route look hints for list input Paolo Abeni
2019-11-21 20:11 ` David Ahern
2019-11-20 12:47 ` [PATCH net-next v4 4/5] ipv4: move fib4_has_custom_rules() helper to public header Paolo Abeni
2019-11-21 20:12 ` David Ahern
2019-11-20 12:47 ` [PATCH net-next v4 5/5] ipv4: use dst hint for ipv4 list receive Paolo Abeni
2019-11-21 21:16 ` David Ahern
2019-11-20 16:54 ` Edward Cree [this message]
2019-11-21 22:46 ` [PATCH net-next v4 0/5] net: introduce and use route hint 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=7b5fe6ee-4fa2-a6bd-890c-160fff3ec74d@solarflare.com \
--to=ecree@solarflare.com \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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).