From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@nvidia.com>
Cc: petrm@nvidia.com, dsahern@gmail.com, taspelund@nvidia.com,
netdev@vger.kernel.org, razor@blackwall.org,
bridge@lists.linux-foundation.org, edumazet@google.com,
roopa@nvidia.com, kuba@kernel.org, pabeni@redhat.com,
davem@davemloft.net
Subject: Re: [Bridge] [PATCH net-next v2 0/4] Add backup nexthop ID support
Date: Wed, 19 Jul 2023 10:10:21 +0000 [thread overview]
Message-ID: <168976142170.5988.10461851053537614919.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230717081229.81917-1-idosch@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Mon, 17 Jul 2023 11:12:25 +0300 you wrote:
> tl;dr
> =====
>
> This patchset adds a new bridge port attribute specifying the nexthop
> object ID to attach to a redirected skb as tunnel metadata. The ID is
> used by the VXLAN driver to choose the target VTEP for the skb. This is
> useful for EVPN multi-homing, where we want to redirect local
> (intra-rack) traffic upon carrier loss through one of the other VTEPs
> (ES peers) connected to the target host.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/4] ip_tunnels: Add nexthop ID field to ip_tunnel_key
https://git.kernel.org/netdev/net-next/c/8bb5e82589f0
- [net-next,v2,2/4] vxlan: Add support for nexthop ID metadata
https://git.kernel.org/netdev/net-next/c/d977e1c8e3a1
- [net-next,v2,3/4] bridge: Add backup nexthop ID support
https://git.kernel.org/netdev/net-next/c/29cfb2aaa442
- [net-next,v2,4/4] selftests: net: Add bridge backup port and backup nexthop ID test
https://git.kernel.org/netdev/net-next/c/b408453053fb
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-07-19 10:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 8:12 [Bridge] [PATCH net-next v2 0/4] Add backup nexthop ID support Ido Schimmel
2023-07-17 8:12 ` [Bridge] [PATCH net-next v2 1/4] ip_tunnels: Add nexthop ID field to ip_tunnel_key Ido Schimmel
2023-07-17 8:12 ` [Bridge] [PATCH net-next v2 2/4] vxlan: Add support for nexthop ID metadata Ido Schimmel
2023-07-17 8:12 ` [Bridge] [PATCH net-next v2 3/4] bridge: Add backup nexthop ID support Ido Schimmel
2023-07-17 8:12 ` [Bridge] [PATCH net-next v2 4/4] selftests: net: Add bridge backup port and backup nexthop ID test Ido Schimmel
2023-07-18 14:43 ` [Bridge] [PATCH net-next v2 0/4] Add backup nexthop ID support David Ahern
2023-07-19 10:10 ` patchwork-bot+netdevbpf [this message]
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=168976142170.5988.10461851053537614919.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.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=razor@blackwall.org \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).