From: David Miller <davem@davemloft.net>
To: dsahern@kernel.org
Cc: netdev@vger.kernel.org, dsahern@gmail.com
Subject: Re: [PATCH net-next] ipv6: Move ipv6 stubs to a separate header file
Date: Sat, 23 Mar 2019 21:40:23 -0400 (EDT) [thread overview]
Message-ID: <20190323.214023.610983922857554034.davem@davemloft.net> (raw)
In-Reply-To: <20190322130609.11655-1-dsahern@kernel.org>
From: David Ahern <dsahern@kernel.org>
Date: Fri, 22 Mar 2019 06:06:09 -0700
> From: David Ahern <dsahern@gmail.com>
>
> The number of stubs is growing and has nothing to do with addrconf.
> Move the definition of the stubs to a separate header file and update
> users. In the move, drop the vxlan specific comment before ipv6_stub.
>
> Code move only; no functional change intended.
>
> Signed-off-by: David Ahern <dsahern@gmail.com>
Eric, I fully support David's overall plan to make separate nexthop
objects as it will significantly empower the stack to do more sensible
things when links flap etc.
If you don't like this road he is going down to achieve that, you must
suggest an alternative.
next prev parent reply other threads:[~2019-03-24 1:40 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 [this message]
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
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=20190323.214023.610983922857554034.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=dsahern@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).