All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org, edumazet@google.com
Subject: Re: [PATCH net-next] ipv6: Move ipv6 stubs to a separate header file
Date: Mon, 25 Mar 2019 20:22:33 -0600	[thread overview]
Message-ID: <6fd90fe8-51bf-60a9-b75e-8028ecb72380@gmail.com> (raw)
In-Reply-To: <20190325032641.5xyav65phoeadgye@ast-mbp>

On 3/24/19 9:26 PM, Alexei Starovoitov wrote:
> The kernel has to be fast as a dataplane but these extra features
> will slow down the routing by making kernel-as-database scale a bit better.

I took Vincent Bernat's fib lookup microbenchmark and added input and
output route lookups to it. Through this commit:

commit 4d5edf447c88e59f5c5716180c1001cde9bf4473
Author: David Ahern <dsahern@gmail.com>
Date:   Mon Mar 11 18:34:48 2019 -0700

    ipv4: Allow ipv6 gateway with ipv4 routes


There is no real measurable difference for IPv4 fib lookups
(fib_lookup), input routes (ip_route_input_rcu) and output routes
(ip_route_output_key_hash_rcu). This is using a bare metal server with a
L5640 Xeon CPU.

The above commit is the target for the first 2 rounds of patches. I will
of course be checking performance each step along the way to nexthop
objects.

  parent reply	other threads:[~2019-03-26  2:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-22 13:06 [PATCH net-next] ipv6: Move ipv6 stubs to a separate header file David Ahern
2019-03-22 16:14 ` Alexei Starovoitov
2019-03-22 16:17   ` David Ahern
2019-03-22 17:04     ` Alexei Starovoitov
2019-03-24  1:40 ` David Miller
2019-03-24  3:55   ` Alexei Starovoitov
2019-03-24 12:56     ` David Ahern
2019-03-25  3:26       ` Alexei Starovoitov
2019-03-25 15:39         ` Stephen Suryaputra
2019-03-25 17:02         ` David Ahern
2019-03-26  3:05           ` Alexei Starovoitov
2019-03-26 14:19             ` David Ahern
2019-03-26 15:11               ` Alexei Starovoitov
2019-03-26 15:29                 ` David Ahern
2019-03-26  2:22         ` David Ahern [this message]
2019-03-29 17:55 ` 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=6fd90fe8-51bf-60a9-b75e-8028ecb72380@gmail.com \
    --to=dsahern@gmail.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=netdev@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.