[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d003b6e7-6db1-f5e3-d356-237e4bf3a34c@blackwall.org>
Date: Thu, 13 Jul 2023 12:29:22 +0300
From: Nikolay Aleksandrov <razor@...ckwall.org>
To: Ido Schimmel <idosch@...dia.com>, netdev@...r.kernel.org,
bridge@...ts.linux-foundation.org
Cc: davem@...emloft.net, kuba@...nel.org, pabeni@...hat.com,
edumazet@...gle.com, roopa@...dia.com, dsahern@...il.com, petrm@...dia.com,
taspelund@...dia.com
Subject: Re: [RFC PATCH net-next 1/4] ip_tunnels: Add nexthop ID field to
ip_tunnel_key
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@...dia.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@...ckwall.org>
Powered by blists - more mailing lists