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 00/15] vxlan: Convert FDB table to rhashtable
Date: Tue, 22 Apr 2025 09:38:24 +0000 [thread overview]
Message-ID: <174531470400.1495352.5589563462825751298.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250415121143.345227-1-idosch@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 15 Apr 2025 15:11:28 +0300 you wrote:
> The VXLAN driver currently stores FDB entries in a hash table with a
> fixed number of buckets (256), resulting in reduced performance as the
> number of entries grows. This patchset solves the issue by converting
> the driver to use rhashtable which maintains a more or less constant
> performance regardless of the number of entries.
>
> Measured transmitted packets per second using a single pktgen thread
> with varying number of entries when the transmitted packet always hits
> the default entry (worst case):
>
> [...]
Here is the summary with links:
- [net-next,01/15] vxlan: Add RCU read-side critical sections in the Tx path
https://git.kernel.org/netdev/net-next/c/804b09be09f8
- [net-next,02/15] vxlan: Simplify creation of default FDB entry
https://git.kernel.org/netdev/net-next/c/884dd448f1ac
- [net-next,03/15] vxlan: Insert FDB into hash table in vxlan_fdb_create()
https://git.kernel.org/netdev/net-next/c/69281e0fe18a
- [net-next,04/15] vxlan: Unsplit default FDB entry creation and notification
https://git.kernel.org/netdev/net-next/c/ccc203b9a846
- [net-next,05/15] vxlan: Relocate assignment of default remote device
https://git.kernel.org/netdev/net-next/c/6ba480cca25f
- [net-next,06/15] vxlan: Use a single lock to protect the FDB table
https://git.kernel.org/netdev/net-next/c/094adad91310
- [net-next,07/15] vxlan: Add a linked list of FDB entries
https://git.kernel.org/netdev/net-next/c/8d45673d2d2e
- [net-next,08/15] vxlan: Use linked list to traverse FDB entries
https://git.kernel.org/netdev/net-next/c/7aa0dc750d4b
- [net-next,09/15] vxlan: Convert FDB garbage collection to RCU
https://git.kernel.org/netdev/net-next/c/a6d04f8937e3
- [net-next,10/15] vxlan: Convert FDB flushing to RCU
https://git.kernel.org/netdev/net-next/c/54f45187b635
- [net-next,11/15] vxlan: Rename FDB Tx lookup function
https://git.kernel.org/netdev/net-next/c/5cde39ea3881
- [net-next,12/15] vxlan: Create wrappers for FDB lookup
https://git.kernel.org/netdev/net-next/c/ebe642067455
- [net-next,13/15] vxlan: Do not treat dst cache initialization errors as fatal
https://git.kernel.org/netdev/net-next/c/20c76dadc783
- [net-next,14/15] vxlan: Introduce FDB key structure
https://git.kernel.org/netdev/net-next/c/f13f3b4157dd
- [net-next,15/15] vxlan: Convert FDB table to rhashtable
https://git.kernel.org/netdev/net-next/c/1f763fa808e9
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-04-22 9:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 12:11 [PATCH net-next 00/15] vxlan: Convert FDB table to rhashtable Ido Schimmel
2025-04-15 12:11 ` [PATCH net-next 01/15] vxlan: Add RCU read-side critical sections in the Tx path Ido Schimmel
2025-04-15 12:11 ` [PATCH net-next 02/15] vxlan: Simplify creation of default FDB entry Ido Schimmel
2025-04-15 12:11 ` [PATCH net-next 03/15] vxlan: Insert FDB into hash table in vxlan_fdb_create() Ido Schimmel
2025-04-15 12:11 ` [PATCH net-next 04/15] vxlan: Unsplit default FDB entry creation and notification Ido Schimmel
2025-04-15 12:11 ` [PATCH net-next 05/15] vxlan: Relocate assignment of default remote device Ido Schimmel
2025-04-15 12:11 ` [PATCH net-next 06/15] vxlan: Use a single lock to protect the FDB table Ido Schimmel
2025-04-15 12:11 ` [PATCH net-next 07/15] vxlan: Add a linked list of FDB entries Ido Schimmel
2025-04-15 12:11 ` [PATCH net-next 08/15] vxlan: Use linked list to traverse " Ido Schimmel
2025-04-15 12:11 ` [PATCH net-next 09/15] vxlan: Convert FDB garbage collection to RCU Ido Schimmel
2025-04-15 12:11 ` [PATCH net-next 10/15] vxlan: Convert FDB flushing " Ido Schimmel
2025-04-15 12:11 ` [PATCH net-next 11/15] vxlan: Rename FDB Tx lookup function Ido Schimmel
2025-04-15 12:11 ` [PATCH net-next 12/15] vxlan: Create wrappers for FDB lookup Ido Schimmel
2025-04-22 8:46 ` Paolo Abeni
2025-04-23 12:21 ` Ido Schimmel
2025-04-15 12:11 ` [PATCH net-next 13/15] vxlan: Do not treat dst cache initialization errors as fatal Ido Schimmel
2025-04-22 8:49 ` Paolo Abeni
2025-04-24 8:18 ` Ido Schimmel
2025-04-15 12:11 ` [PATCH net-next 14/15] vxlan: Introduce FDB key structure Ido Schimmel
2025-04-15 12:11 ` [PATCH net-next 15/15] vxlan: Convert FDB table to rhashtable Ido Schimmel
2025-04-15 14:15 ` [PATCH net-next 00/15] " Nikolay Aleksandrov
2025-04-22 9:38 ` 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=174531470400.1495352.5589563462825751298.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).