From: David Ahern <dsahern@kernel.org>
To: Hangbin Liu <liuhangbin@gmail.com>,
Nicolas Dichtel <nicolas.dichtel@6wind.com>
Cc: netdev@vger.kernel.org, "David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Ido Schimmel <idosch@idosch.org>,
Thomas Haller <thaller@redhat.com>
Subject: Re: [PATCH net-next] ipv6: do not merge differe type and protocol routes
Date: Thu, 14 Sep 2023 21:08:18 -0600 [thread overview]
Message-ID: <c5a71b96-30aa-4543-2d8e-196a37693254@kernel.org> (raw)
In-Reply-To: <ZQPAL84/w323CgNT@Laptop-X1>
On 9/14/23 8:23 PM, Hangbin Liu wrote:
> On Fri, Sep 01, 2023 at 11:36:51AM +0200, Nicolas Dichtel wrote:
>>> I do agree now that protocol is informative (passthrough from the kernel
>>> perspective) so not really part of the route. That should be dropped
>
> I'm not sure. Is there any user space route daemon will use this info? e.g. some
> BGP route daemon?
It is passthrough information for userspace to track who installed the
route. It is not part of the route itself, but metadata passed in and
returned.
next prev parent reply other threads:[~2023-09-15 3:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 6:15 [PATCH net-next] ipv6: do not merge differe type and protocol routes Hangbin Liu
2023-08-30 14:49 ` David Ahern
2023-08-30 23:51 ` Hangbin Liu
2023-08-30 15:29 ` Nicolas Dichtel
2023-08-30 18:57 ` David Ahern
2023-08-31 8:17 ` Nicolas Dichtel
2023-08-31 10:14 ` Hangbin Liu
2023-08-31 11:58 ` Nicolas Dichtel
2023-08-31 18:27 ` David Ahern
2023-09-01 9:36 ` Nicolas Dichtel
2023-09-15 2:23 ` Hangbin Liu
2023-09-15 3:08 ` David Ahern [this message]
2023-09-15 10:02 ` Hangbin Liu
2023-09-01 3:58 ` Hangbin Liu
2023-09-01 9:50 ` Nicolas Dichtel
2023-09-15 3:49 ` Hangbin Liu
2023-09-15 15:58 ` Nicolas Dichtel
-- strict thread matches above, loose matches on Subject: below --
2023-08-30 6:16 Hangbin Liu
2023-08-30 9:37 ` Hangbin Liu
2023-08-30 9:48 ` Hangbin Liu
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=c5a71b96-30aa-4543-2d8e-196a37693254@kernel.org \
--to=dsahern@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@idosch.org \
--cc=kuba@kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pabeni@redhat.com \
--cc=thaller@redhat.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).