All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Nikolay Aleksandrov <razor@blackwall.org>
Cc: netdev@vger.kernel.org, idosch@nvidia.com, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, bridge@lists.linux.dev
Subject: Re: [PATCH net-next 00/12] net: bridge: vlan: optimize standard fdb fwding path
Date: Fri, 02 Oct 2026 20:00:13 +0000	[thread overview]
Message-ID: <179097121302.3565478.15729563050864292363.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260930071411.2786201-1-razor@blackwall.org>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Wed, 30 Sep 2026 10:13:59 +0300 you wrote:
> Hi,
> This patch-set is a follow-up after the bridge flood fwding path
> optimizations and applies the same idea to the standard fdb fwding path.
> We are able to remove 2 vlan hash lookups in the standard fdb fwding
> path by caching the port-VLAN pointer in the fdb, to do that we switch the
> fdb dst to an opaque type that can be either a port pointer or vlan pointer
> differentiated by a bit. The field is a struct and also has a __private tag
> so we can catch direct users, it should be used only via the helpers.
> Sharing a field makes it easier to pass it around and also allows us to
> save struct space for the fast-path. Interesting case is when an fdb is
> promoted from a raw port to port-VLAN on the same port, it needs to be
> handled carefully so we use cmpxchg to make sure we don't generate
> deletion/replace notifications because it doesn't change the port.
> I tested VLAN deletion after these changes (we now wait a grace period for
> every delete) and the hit was ~20% reduction in deleted VLANs / sec
> deleting 4k VLANs took 14ms more and on my VM the VLANs deleted / sec went
> from 63k to 52k / sec. The complexity to batch them is not worth it.
> 
> [...]

Here is the summary with links:
  - [net-next,01/12] net: bridge: introduce a bridge destination type
    https://git.kernel.org/netdev/net-next/c/13bb47965e02
  - [net-next,02/12] net: bridge: use net_bridge_dst for fdb destinations
    https://git.kernel.org/netdev/net-next/c/fd7a8eb03c32
  - [net-next,03/12] net: bridge: add VLAN support to bridge destinations
    https://git.kernel.org/netdev/net-next/c/a39c339fd6c5
  - [net-next,04/12] net: bridge: vlan: return VLAN entries from ingress helpers
    https://git.kernel.org/netdev/net-next/c/cebd6130e6c2
  - [net-next,05/12] net: bridge: fdb: pass VLAN entries to learning updates
    https://git.kernel.org/netdev/net-next/c/8247ef76032b
  - [net-next,06/12] net: bridge: fdb: consolidate port-VLAN cleanup
    https://git.kernel.org/netdev/net-next/c/f0a349b92120
  - [net-next,07/12] net: bridge: vlan: split unpublishing from deletion
    https://git.kernel.org/netdev/net-next/c/e5c71bf91447
  - [net-next,08/12] net: bridge: vlan: quiesce readers before freeing port VLANs
    https://git.kernel.org/netdev/net-next/c/83edc87a9172
  - [net-next,09/12] net: bridge: fdb: factor out existing entry updates
    https://git.kernel.org/netdev/net-next/c/941056f91907
  - [net-next,10/12] net: bridge: fdb: cache port VLANs in learned entries
    https://git.kernel.org/netdev/net-next/c/8009eb405fc6
  - [net-next,11/12] net: bridge: fdb: cache VLAN destinations in configured entries
    https://git.kernel.org/netdev/net-next/c/8533e9b85bd2
  - [net-next,12/12] net: bridge: fdb: avoid VLAN lookups in unicast forwarding
    https://git.kernel.org/netdev/net-next/c/f1829618e0ad

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-10-02 20:00 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30  7:13 [PATCH net-next 00/12] net: bridge: vlan: optimize standard fdb fwding path Nikolay Aleksandrov
2026-09-30  7:14 ` [PATCH net-next 01/12] net: bridge: introduce a bridge destination type Nikolay Aleksandrov
2026-10-01  7:24   ` Nikolay Aleksandrov
2026-10-02 19:45   ` Jakub Kicinski
2026-10-02 20:09     ` Nikolay Aleksandrov
2026-10-02 20:18       ` Jakub Kicinski
2026-09-30  7:14 ` [PATCH net-next 02/12] net: bridge: use net_bridge_dst for fdb destinations Nikolay Aleksandrov
2026-09-30  7:14 ` [PATCH net-next 03/12] net: bridge: add VLAN support to bridge destinations Nikolay Aleksandrov
2026-10-01 11:59   ` netdev-bot+sashiko
2026-10-01 12:03     ` Nikolay Aleksandrov
2026-09-30  7:14 ` [PATCH net-next 04/12] net: bridge: vlan: return VLAN entries from ingress helpers Nikolay Aleksandrov
2026-09-30  7:14 ` [PATCH net-next 05/12] net: bridge: fdb: pass VLAN entries to learning updates Nikolay Aleksandrov
2026-09-30  7:14 ` [PATCH net-next 06/12] net: bridge: fdb: consolidate port-VLAN cleanup Nikolay Aleksandrov
2026-10-01 11:59   ` netdev-bot+sashiko
2026-10-01 12:05     ` Nikolay Aleksandrov
2026-09-30  7:14 ` [PATCH net-next 07/12] net: bridge: vlan: split unpublishing from deletion Nikolay Aleksandrov
2026-09-30  7:14 ` [PATCH net-next 08/12] net: bridge: vlan: quiesce readers before freeing port VLANs Nikolay Aleksandrov
2026-10-01  7:28   ` Nikolay Aleksandrov
2026-10-01 11:59   ` netdev-bot+sashiko
2026-10-01 12:07     ` Nikolay Aleksandrov
2026-10-02 19:50       ` Jakub Kicinski
2026-10-02 19:59         ` Nikolay Aleksandrov
2026-09-30  7:14 ` [PATCH net-next 09/12] net: bridge: fdb: factor out existing entry updates Nikolay Aleksandrov
2026-09-30  7:14 ` [PATCH net-next 10/12] net: bridge: fdb: cache port VLANs in learned entries Nikolay Aleksandrov
2026-09-30  7:14 ` [PATCH net-next 11/12] net: bridge: fdb: cache VLAN destinations in configured entries Nikolay Aleksandrov
2026-10-01  7:36   ` Nikolay Aleksandrov
2026-09-30  7:14 ` [PATCH net-next 12/12] net: bridge: fdb: avoid VLAN lookups in unicast forwarding Nikolay Aleksandrov
2026-10-02 20:00 ` 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=179097121302.3565478.15729563050864292363.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bridge@lists.linux.dev \
    --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=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 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.