From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@nvidia.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com, andrew+netdev@lunn.ch,
horms@kernel.org, petrm@nvidia.com, razor@blackwall.org
Subject: Re: [PATCH net-next 0/8] vxlan: Age FDB entries based on Rx traffic
Date: Thu, 06 Feb 2025 04:40:32 +0000 [thread overview]
Message-ID: <173881683280.1004532.16490678927076536825.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250204145549.1216254-1-idosch@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 4 Feb 2025 16:55:41 +0200 you wrote:
> tl;dr - This patchset prevents VXLAN FDB entries from lingering if
> traffic is only forwarded to a silent host.
>
> The VXLAN driver maintains two timestamps for each FDB entry: 'used' and
> 'updated'. The first is refreshed by both the Rx and Tx paths and the
> second is refreshed upon migration.
>
> [...]
Here is the summary with links:
- [net-next,1/8] vxlan: Annotate FDB data races
https://git.kernel.org/netdev/net-next/c/f6205f8215f1
- [net-next,2/8] vxlan: Read jiffies once when updating FDB 'used' time
https://git.kernel.org/netdev/net-next/c/1370c45d6e7e
- [net-next,3/8] vxlan: Always refresh FDB 'updated' time when learning is enabled
https://git.kernel.org/netdev/net-next/c/c4f2082bf641
- [net-next,4/8] vxlan: Refresh FDB 'updated' time upon 'NTF_USE'
https://git.kernel.org/netdev/net-next/c/40a9994f2fbd
- [net-next,5/8] vxlan: Refresh FDB 'updated' time upon user space updates
https://git.kernel.org/netdev/net-next/c/fb2f449eca51
- [net-next,6/8] vxlan: Age out FDB entries based on 'updated' time
https://git.kernel.org/netdev/net-next/c/b4a1d98b0fa5
- [net-next,7/8] vxlan: Avoid unnecessary updates to FDB 'used' time
https://git.kernel.org/netdev/net-next/c/9722f834fe9a
- [net-next,8/8] selftests: forwarding: vxlan_bridge_1d: Check aging while forwarding
https://git.kernel.org/netdev/net-next/c/c467a98e1de0
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:[~2025-02-06 4:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 14:55 [PATCH net-next 0/8] vxlan: Age FDB entries based on Rx traffic Ido Schimmel
2025-02-04 14:55 ` [PATCH net-next 1/8] vxlan: Annotate FDB data races Ido Schimmel
2025-02-04 15:41 ` Eric Dumazet
2025-02-04 16:36 ` Nikolay Aleksandrov
2025-02-04 14:55 ` [PATCH net-next 2/8] vxlan: Read jiffies once when updating FDB 'used' time Ido Schimmel
2025-02-04 15:42 ` Eric Dumazet
2025-02-04 16:36 ` Nikolay Aleksandrov
2025-02-04 14:55 ` [PATCH net-next 3/8] vxlan: Always refresh FDB 'updated' time when learning is enabled Ido Schimmel
2025-02-04 16:37 ` Nikolay Aleksandrov
2025-02-04 14:55 ` [PATCH net-next 4/8] vxlan: Refresh FDB 'updated' time upon 'NTF_USE' Ido Schimmel
2025-02-04 16:37 ` Nikolay Aleksandrov
2025-02-04 14:55 ` [PATCH net-next 5/8] vxlan: Refresh FDB 'updated' time upon user space updates Ido Schimmel
2025-02-04 16:37 ` Nikolay Aleksandrov
2025-02-04 14:55 ` [PATCH net-next 6/8] vxlan: Age out FDB entries based on 'updated' time Ido Schimmel
2025-02-04 16:38 ` Nikolay Aleksandrov
2025-02-04 14:55 ` [PATCH net-next 7/8] vxlan: Avoid unnecessary updates to FDB 'used' time Ido Schimmel
2025-02-04 16:38 ` Nikolay Aleksandrov
2025-02-04 14:55 ` [PATCH net-next 8/8] selftests: forwarding: vxlan_bridge_1d: Check aging while forwarding Ido Schimmel
2025-02-04 16:38 ` Nikolay Aleksandrov
2025-02-06 4:40 ` 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=173881683280.1004532.16490678927076536825.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--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 \
/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).