From: Nikolay Aleksandrov <razor@blackwall.org>
To: Ido Schimmel <idosch@nvidia.com>,
netdev@vger.kernel.org, bridge@lists.linux-foundation.org
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, roopa@nvidia.com, dsahern@gmail.com,
petrm@nvidia.com, taspelund@nvidia.com
Subject: Re: [RFC PATCH net-next 1/4] ip_tunnels: Add nexthop ID field to ip_tunnel_key
Date: Thu, 13 Jul 2023 12:29:22 +0300 [thread overview]
Message-ID: <d003b6e7-6db1-f5e3-d356-237e4bf3a34c@blackwall.org> (raw)
In-Reply-To: <20230713070925.3955850-2-idosch@nvidia.com>
On 13/07/2023 10:09, Ido Schimmel wrote:
> Extend the ip_tunnel_key structure with a field indicating the ID of the
> nexthop object via which the skb should be routed.
>
> The field is going to be populated in subsequent patches by the bridge
> driver in order to indicate to the VXLAN driver which FDB nexthop object
> to use in order to reach the target host.
>
> Signed-off-by: Ido Schimmel <idosch@nvidia.com>
> ---
> include/net/ip_tunnels.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/net/ip_tunnels.h b/include/net/ip_tunnels.h
> index ed4b6ad3fcac..e8750b4ef7e1 100644
> --- a/include/net/ip_tunnels.h
> +++ b/include/net/ip_tunnels.h
> @@ -52,6 +52,7 @@ struct ip_tunnel_key {
> u8 tos; /* TOS for IPv4, TC for IPv6 */
> u8 ttl; /* TTL for IPv4, HL for IPv6 */
> __be32 label; /* Flow Label for IPv6 */
> + u32 nhid;
> __be16 tp_src;
> __be16 tp_dst;
> __u8 flow_flags;
Reviewed-by: Nikolay Aleksandrov <razor@blackwall.org>
next prev parent reply other threads:[~2023-07-13 9:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 7:09 [RFC PATCH net-next 0/4] Add backup nexthop ID support Ido Schimmel
2023-07-13 7:09 ` [RFC PATCH net-next 1/4] ip_tunnels: Add nexthop ID field to ip_tunnel_key Ido Schimmel
2023-07-13 9:29 ` Nikolay Aleksandrov [this message]
2023-07-13 7:09 ` [RFC PATCH net-next 2/4] vxlan: Add support for nexthop ID metadata Ido Schimmel
2023-07-13 9:30 ` Nikolay Aleksandrov
2023-07-13 7:09 ` [RFC PATCH net-next 3/4] bridge: Add backup nexthop ID support Ido Schimmel
2023-07-13 9:33 ` Nikolay Aleksandrov
2023-07-13 9:46 ` Nikolay Aleksandrov
2023-07-13 7:09 ` [RFC PATCH net-next 4/4] selftests: net: Add bridge backup port and backup nexthop ID test Ido Schimmel
2023-07-13 9:34 ` Nikolay Aleksandrov
2023-07-14 17:01 ` [RFC PATCH net-next 0/4] Add backup nexthop ID support David Ahern
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=d003b6e7-6db1-f5e3-d356-237e4bf3a34c@blackwall.org \
--to=razor@blackwall.org \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=roopa@nvidia.com \
--cc=taspelund@nvidia.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).