From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@nvidia.com>
Cc: netdev@vger.kernel.org, razor@blackwall.org,
bridge@lists.linux-foundation.org, edumazet@google.com,
mlxsw@nvidia.com, roopa@nvidia.com, kuba@kernel.org,
pabeni@redhat.com, davem@davemloft.net
Subject: Re: [Bridge] [PATCH net-next v2 0/9] bridge: Add per-{Port, VLAN} neighbor suppression
Date: Fri, 21 Apr 2023 07:50:30 +0000 [thread overview]
Message-ID: <168206343031.30967.17590346122475626236.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230419153500.2655036-1-idosch@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Wed, 19 Apr 2023 18:34:51 +0300 you wrote:
> Background
> ==========
>
> In order to minimize the flooding of ARP and ND messages in the VXLAN
> network, EVPN includes provisions [1] that allow participating VTEPs to
> suppress such messages in case they know the MAC-IP binding and can
> reply on behalf of the remote host. In Linux, the above is implemented
> in the bridge driver using a per-port option called "neigh_suppress"
> that was added in kernel version 4.15 [2].
>
> [...]
Here is the summary with links:
- [net-next,v2,1/9] bridge: Reorder neighbor suppression check when flooding
https://git.kernel.org/netdev/net-next/c/013a7ce81dd8
- [net-next,v2,2/9] bridge: Pass VLAN ID to br_flood()
https://git.kernel.org/netdev/net-next/c/e408336a693e
- [net-next,v2,3/9] bridge: Add internal flags for per-{Port, VLAN} neighbor suppression
https://git.kernel.org/netdev/net-next/c/a714e3ec2308
- [net-next,v2,4/9] bridge: Take per-{Port, VLAN} neighbor suppression into account
https://git.kernel.org/netdev/net-next/c/6be42ed0a5f4
- [net-next,v2,5/9] bridge: Encapsulate data path neighbor suppression logic
https://git.kernel.org/netdev/net-next/c/3aca683e0654
- [net-next,v2,6/9] bridge: Add per-{Port, VLAN} neighbor suppression data path support
https://git.kernel.org/netdev/net-next/c/412614b1457a
- [net-next,v2,7/9] bridge: vlan: Allow setting VLAN neighbor suppression state
https://git.kernel.org/netdev/net-next/c/83f6d600796c
- [net-next,v2,8/9] bridge: Allow setting per-{Port, VLAN} neighbor suppression state
https://git.kernel.org/netdev/net-next/c/160656d7201d
- [net-next,v2,9/9] selftests: net: Add bridge neighbor suppression test
https://git.kernel.org/netdev/net-next/c/7648ac72dcd7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@nvidia.com>
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, razor@blackwall.org, roopa@nvidia.com,
mlxsw@nvidia.com
Subject: Re: [PATCH net-next v2 0/9] bridge: Add per-{Port, VLAN} neighbor suppression
Date: Fri, 21 Apr 2023 07:50:30 +0000 [thread overview]
Message-ID: <168206343031.30967.17590346122475626236.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230419153500.2655036-1-idosch@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Wed, 19 Apr 2023 18:34:51 +0300 you wrote:
> Background
> ==========
>
> In order to minimize the flooding of ARP and ND messages in the VXLAN
> network, EVPN includes provisions [1] that allow participating VTEPs to
> suppress such messages in case they know the MAC-IP binding and can
> reply on behalf of the remote host. In Linux, the above is implemented
> in the bridge driver using a per-port option called "neigh_suppress"
> that was added in kernel version 4.15 [2].
>
> [...]
Here is the summary with links:
- [net-next,v2,1/9] bridge: Reorder neighbor suppression check when flooding
https://git.kernel.org/netdev/net-next/c/013a7ce81dd8
- [net-next,v2,2/9] bridge: Pass VLAN ID to br_flood()
https://git.kernel.org/netdev/net-next/c/e408336a693e
- [net-next,v2,3/9] bridge: Add internal flags for per-{Port, VLAN} neighbor suppression
https://git.kernel.org/netdev/net-next/c/a714e3ec2308
- [net-next,v2,4/9] bridge: Take per-{Port, VLAN} neighbor suppression into account
https://git.kernel.org/netdev/net-next/c/6be42ed0a5f4
- [net-next,v2,5/9] bridge: Encapsulate data path neighbor suppression logic
https://git.kernel.org/netdev/net-next/c/3aca683e0654
- [net-next,v2,6/9] bridge: Add per-{Port, VLAN} neighbor suppression data path support
https://git.kernel.org/netdev/net-next/c/412614b1457a
- [net-next,v2,7/9] bridge: vlan: Allow setting VLAN neighbor suppression state
https://git.kernel.org/netdev/net-next/c/83f6d600796c
- [net-next,v2,8/9] bridge: Allow setting per-{Port, VLAN} neighbor suppression state
https://git.kernel.org/netdev/net-next/c/160656d7201d
- [net-next,v2,9/9] selftests: net: Add bridge neighbor suppression test
https://git.kernel.org/netdev/net-next/c/7648ac72dcd7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-04-21 7:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 15:34 [Bridge] [PATCH net-next v2 0/9] bridge: Add per-{Port, VLAN} neighbor suppression Ido Schimmel
2023-04-19 15:34 ` Ido Schimmel
2023-04-19 15:34 ` [Bridge] [PATCH net-next v2 1/9] bridge: Reorder neighbor suppression check when flooding Ido Schimmel
2023-04-19 15:34 ` Ido Schimmel
2023-04-19 15:34 ` [Bridge] [PATCH net-next v2 2/9] bridge: Pass VLAN ID to br_flood() Ido Schimmel
2023-04-19 15:34 ` Ido Schimmel
2023-04-19 15:34 ` [Bridge] [PATCH net-next v2 3/9] bridge: Add internal flags for per-{Port, VLAN} neighbor suppression Ido Schimmel
2023-04-19 15:34 ` Ido Schimmel
2023-04-19 15:34 ` [Bridge] [PATCH net-next v2 4/9] bridge: Take per-{Port, VLAN} neighbor suppression into account Ido Schimmel
2023-04-19 15:34 ` Ido Schimmel
2023-04-19 15:34 ` [Bridge] [PATCH net-next v2 5/9] bridge: Encapsulate data path neighbor suppression logic Ido Schimmel
2023-04-19 15:34 ` Ido Schimmel
2023-04-19 15:34 ` [Bridge] [PATCH net-next v2 6/9] bridge: Add per-{Port, VLAN} neighbor suppression data path support Ido Schimmel
2023-04-19 15:34 ` Ido Schimmel
2023-04-19 15:34 ` [Bridge] [PATCH net-next v2 7/9] bridge: vlan: Allow setting VLAN neighbor suppression state Ido Schimmel
2023-04-19 15:34 ` Ido Schimmel
2023-04-19 15:34 ` [Bridge] [PATCH net-next v2 8/9] bridge: Allow setting per-{Port, VLAN} " Ido Schimmel
2023-04-19 15:34 ` Ido Schimmel
2023-04-19 15:35 ` [Bridge] [PATCH net-next v2 9/9] selftests: net: Add bridge neighbor suppression test Ido Schimmel
2023-04-19 15:35 ` Ido Schimmel
2023-04-21 7:50 ` patchwork-bot+netdevbpf [this message]
2023-04-21 7:50 ` [PATCH net-next v2 0/9] bridge: Add per-{Port, VLAN} neighbor suppression patchwork-bot+netdevbpf
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=168206343031.30967.17590346122475626236.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=roopa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.