Netdev List
 help / color / mirror / Atom feed
From: Nikolay Aleksandrov <razor@blackwall.org>
To: netdev@vger.kernel.org
Cc: idosch@nvidia.com, davem@davemloft.net, edumazet@kernel.org,
	kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
	bridge@lists.linux.dev, Nikolay Aleksandrov <razor@blackwall.org>
Subject: [PATCH net-next 0/6] net: bridge: fwd optimization cleanups
Date: Mon,  5 Oct 2026 17:39:31 +0300	[thread overview]
Message-ID: <20261005143937.877466-1-razor@blackwall.org> (raw)

Hi,
This patch-set takes care of the review comments and also does some
additional cleanups after the recent forwarding optimizations. The first
patch and the fourth take care of Ido's comments[1]. I have folded his
suggestion with inlining the pvid helpers which aren't necessary anymore.
The second patch takes care of Sashiko's comment[2]. The rest are
additional cleanups. No functional changes intended by any of these.
For more information please check their commit messages.

I do have one more separate patch-set which removes more VLAN lookups,
this one is only about following up on comments and minor cleanups.

[1] https://lore.kernel.org/netdev/20260921134458.GA2199421@shredder/
[2] https://lore.kernel.org/netdev/179085595018.434549.16034696945314071975@kernel.org/

Thanks,
 Nik

Nikolay Aleksandrov (6):
  net: bridge: rename dst to fwd in br_flood_vlan
  net: bridge: fdb: update the comment for br_fdb_cleanup_by_dst
  net: bridge: vlan: share VLAN validation in br_should_learn
  net: bridge: vlan: inline pvid pointer updates
  net: bridge: fdb: factor out configured entry destination updates
  net: bridge: fdb: use the entry key in __fdb_update

 net/bridge/br_fdb.c     | 51 ++++++++++++++++++++++------------------
 net/bridge/br_forward.c | 14 +++++------
 net/bridge/br_vlan.c    | 52 +++++++++++++----------------------------
 3 files changed, 51 insertions(+), 66 deletions(-)

-- 
2.47.3


             reply	other threads:[~2026-10-05 14:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-05 14:39 Nikolay Aleksandrov [this message]
2026-10-05 14:39 ` [PATCH net-next 1/6] net: bridge: rename dst to fwd in br_flood_vlan Nikolay Aleksandrov
2026-10-05 14:39 ` [PATCH net-next 2/6] net: bridge: fdb: update the comment for br_fdb_cleanup_by_dst Nikolay Aleksandrov
2026-10-05 14:39 ` [PATCH net-next 3/6] net: bridge: vlan: share VLAN validation in br_should_learn Nikolay Aleksandrov
2026-10-05 14:39 ` [PATCH net-next 4/6] net: bridge: vlan: inline pvid pointer updates Nikolay Aleksandrov
2026-10-05 14:39 ` [PATCH net-next 5/6] net: bridge: fdb: factor out configured entry destination updates Nikolay Aleksandrov
2026-10-05 14:39 ` [PATCH net-next 6/6] net: bridge: fdb: use the entry key in __fdb_update Nikolay Aleksandrov
2026-10-06 12:39 ` [PATCH net-next 0/6] net: bridge: fwd optimization cleanups Ido Schimmel
2026-10-07  1:30 ` 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=20261005143937.877466-1-razor@blackwall.org \
    --to=razor@blackwall.org \
    --cc=bridge@lists.linux.dev \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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