From: David Ahern <dsahern@gmail.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>,
Edward Cree <ecree@solarflare.com>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: [PATCH net-next v4 3/5] ipv6: introduce and uses route look hints for list input.
Date: Thu, 21 Nov 2019 13:11:42 -0700 [thread overview]
Message-ID: <9efbe588-6fe9-fd9e-cd37-1779cfd00343@gmail.com> (raw)
In-Reply-To: <af831ed39b697b86cd380d67b976438156d04da2.1574252982.git.pabeni@redhat.com>
On 11/20/19 5:47 AM, Paolo Abeni wrote:
> When doing RX batch packet processing, we currently always repeat
> the route lookup for each ingress packet. When no custom rules are
> in place, and there aren't routes depending on source addresses,
> we know that packets with the same destination address will use
> the same dst.
>
> This change tries to avoid per packet route lookup caching
> the destination address of the latest successful lookup, and
> reusing it for the next packet when the above conditions are
> in place. Ingress traffic for most servers should fit.
>
> The measured performance delta under UDP flood vs a recvmmsg
> receiver is as follow:
>
> vanilla patched delta
> Kpps Kpps %
> 1431 1674 +17
>
> In the worst-case scenario - each packet has a different
> destination address - the performance delta is within noise
> range.
>
...
>
> Signed-off-by: Paolo Abeni <pabeni@redhat.com>
> ---
> net/ipv6/ip6_input.c | 26 ++++++++++++++++++++++++--
> 1 file changed, 24 insertions(+), 2 deletions(-)
Reviewed-by: David Ahern <dsahern@gmail.com>
next prev parent reply other threads:[~2019-11-21 20:11 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 [this message]
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 ` [PATCH net-next v4 0/5] net: introduce and use route hint Edward Cree
2019-11-21 22:46 ` 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=9efbe588-6fe9-fd9e-cd37-1779cfd00343@gmail.com \
--to=dsahern@gmail.com \
--cc=davem@davemloft.net \
--cc=ecree@solarflare.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).