Netdev List
 help / color / mirror / Atom feed
From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: David Ahern <dsahern@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: Sun, 24 Mar 2019 20:26:43 -0700	[thread overview]
Message-ID: <20190325032641.5xyav65phoeadgye@ast-mbp> (raw)
In-Reply-To: <c428aa96-8570-1064-a37b-7b030cfa0a5a@gmail.com>

On Sun, Mar 24, 2019 at 06:56:42AM -0600, David Ahern wrote:
> 
> This change also enables many other key features:
> 1. IPv4 multipath routes are not evicted just because 1 hop goes down.
> 2. IPv6 multipath routes with device only nexthops (e.g., tunnels).
> 3. IPv6 nexthop with IPv4 route (aka, RFC 5549) which enables a more
> natural BGP unnumbered.
> 4. Lower memory consumption for IPv6 FIB entries which has no sharing at
> all like IPv4 does.
> 5. Allows atomic update of nexthop definitions with a single replace
> command as opposed to replacing the N-routes using it.

Does kernel work as data plane or control plane in any of the above
features ?
Sadly the patches allow it to do both, but cumulus doesn't use it
for data path. The kernel on control plane cpu is merely a database.
And today it doesn't scale when used as a database.
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.
Hence my suggestion in the previous email: use proper database
to store routes, nexthops and whatever else necessary to program the asic.
The kernel doesn't need to hold this information.


  reply	other threads:[~2019-03-25  3:26 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 [this message]
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
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=20190325032641.5xyav65phoeadgye@ast-mbp \
    --to=alexei.starovoitov@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox