From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, f.fainelli@gmail.com, andrew@lunn.ch,
vivien.didelot@gmail.com, tobias@waldekranz.com,
dqfext@gmail.com, alsi@bang-olufsen.dk, kurt@linutronix.de,
hauke@hauke-m.de, woojung.huh@microchip.com,
UNGLinuxDriver@microchip.com, sean.wang@mediatek.com,
Landen.Chao@mediatek.com, matthias.bgg@gmail.com,
claudiu.manoil@nxp.com, alexandre.belloni@bootlin.com,
linus.walleij@linaro.org, george.mccollister@gmail.com
Subject: Re: [PATCH v3 net-next 00/12] Rework DSA bridge TX forwarding offload API
Date: Wed, 08 Dec 2021 23:00:11 +0000 [thread overview]
Message-ID: <163900441145.10579.9768228984013599543.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211206165758.1553882-1-vladimir.oltean@nxp.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 6 Dec 2021 18:57:46 +0200 you wrote:
> This change set is preparation work for DSA support of bridge FDB
> isolation. It replaces struct net_device *dp->bridge_dev with a struct
> dsa_bridge *dp->bridge that contains some extra information about that
> bridge, like a unique number kept by DSA.
>
> Up until now we computed that number only with the bridge TX forwarding
> offload feature, but it will be needed for other features too, like for
> isolation of FDB entries belonging to different bridges. Hardware
> implementations vary, but one common pattern seems to be the presence of
> a FID field which can be associated with that bridge number kept by DSA.
> The idea was outlined here:
> https://patchwork.kernel.org/project/netdevbpf/patch/20210818120150.892647-16-vladimir.oltean@nxp.com/
> (the difference being that with this new proposal, drivers would not
> need to call dsa_bridge_num_find, instead the bridge_num would be part
> of the struct dsa_bridge :: num passed as argument).
>
> [...]
Here is the summary with links:
- [v3,net-next,01/12] net: dsa: make dp->bridge_num one-based
https://git.kernel.org/netdev/net-next/c/3f9bb0301d50
- [v3,net-next,02/12] net: dsa: assign a bridge number even without TX forwarding offload
https://git.kernel.org/netdev/net-next/c/947c8746e2c3
- [v3,net-next,03/12] net: dsa: mt7530: iterate using dsa_switch_for_each_user_port in bridging ops
https://git.kernel.org/netdev/net-next/c/872bb81dfbc3
- [v3,net-next,04/12] net: dsa: mv88e6xxx: iterate using dsa_switch_for_each_user_port in mv88e6xxx_port_check_hw_vlan
https://git.kernel.org/netdev/net-next/c/0493fa7927af
- [v3,net-next,05/12] net: dsa: mv88e6xxx: compute port vlan membership based on dp->bridge_dev comparison
https://git.kernel.org/netdev/net-next/c/65144067d360
- [v3,net-next,06/12] net: dsa: hide dp->bridge_dev and dp->bridge_num in the core behind helpers
https://git.kernel.org/netdev/net-next/c/36cbf39b5690
- [v3,net-next,07/12] net: dsa: hide dp->bridge_dev and dp->bridge_num in drivers behind helpers
https://git.kernel.org/netdev/net-next/c/41fb0cf1bced
- [v3,net-next,08/12] net: dsa: rename dsa_port_offloads_bridge to dsa_port_offloads_bridge_dev
https://git.kernel.org/netdev/net-next/c/936db8a2dba2
- [v3,net-next,09/12] net: dsa: export bridging offload helpers to drivers
https://git.kernel.org/netdev/net-next/c/6a43cba30340
- [v3,net-next,10/12] net: dsa: keep the bridge_dev and bridge_num as part of the same structure
https://git.kernel.org/netdev/net-next/c/d3eed0e57d5d
- [v3,net-next,11/12] net: dsa: add a "tx_fwd_offload" argument to ->port_bridge_join
https://git.kernel.org/netdev/net-next/c/b079922ba2ac
- [v3,net-next,12/12] net: dsa: eliminate dsa_switch_ops :: port_bridge_tx_fwd_{,un}offload
https://git.kernel.org/netdev/net-next/c/857fdd74fb38
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:[~2021-12-08 23:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 16:57 [PATCH v3 net-next 00/12] Rework DSA bridge TX forwarding offload API Vladimir Oltean
2021-12-06 16:57 ` [PATCH v3 net-next 01/12] net: dsa: make dp->bridge_num one-based Vladimir Oltean
2021-12-06 16:57 ` [PATCH v3 net-next 02/12] net: dsa: assign a bridge number even without TX forwarding offload Vladimir Oltean
2021-12-06 16:57 ` [PATCH v3 net-next 03/12] net: dsa: mt7530: iterate using dsa_switch_for_each_user_port in bridging ops Vladimir Oltean
2021-12-06 16:57 ` [PATCH v3 net-next 04/12] net: dsa: mv88e6xxx: iterate using dsa_switch_for_each_user_port in mv88e6xxx_port_check_hw_vlan Vladimir Oltean
2021-12-06 16:57 ` [PATCH v3 net-next 05/12] net: dsa: mv88e6xxx: compute port vlan membership based on dp->bridge_dev comparison Vladimir Oltean
2021-12-06 16:57 ` [PATCH v3 net-next 06/12] net: dsa: hide dp->bridge_dev and dp->bridge_num in the core behind helpers Vladimir Oltean
2021-12-06 16:57 ` [PATCH v3 net-next 07/12] net: dsa: hide dp->bridge_dev and dp->bridge_num in drivers " Vladimir Oltean
2021-12-06 16:57 ` [PATCH v3 net-next 08/12] net: dsa: rename dsa_port_offloads_bridge to dsa_port_offloads_bridge_dev Vladimir Oltean
2021-12-06 16:57 ` [PATCH v3 net-next 09/12] net: dsa: export bridging offload helpers to drivers Vladimir Oltean
2021-12-06 16:57 ` [PATCH v3 net-next 10/12] net: dsa: keep the bridge_dev and bridge_num as part of the same structure Vladimir Oltean
2021-12-06 16:57 ` [PATCH v3 net-next 11/12] net: dsa: add a "tx_fwd_offload" argument to ->port_bridge_join Vladimir Oltean
2021-12-06 16:57 ` [PATCH v3 net-next 12/12] net: dsa: eliminate dsa_switch_ops :: port_bridge_tx_fwd_{,un}offload Vladimir Oltean
2021-12-08 23: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=163900441145.10579.9768228984013599543.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Landen.Chao@mediatek.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=alsi@bang-olufsen.dk \
--cc=andrew@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=dqfext@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=george.mccollister@gmail.com \
--cc=hauke@hauke-m.de \
--cc=kurt@linutronix.de \
--cc=linus.walleij@linaro.org \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sean.wang@mediatek.com \
--cc=tobias@waldekranz.com \
--cc=vivien.didelot@gmail.com \
--cc=vladimir.oltean@nxp.com \
--cc=woojung.huh@microchip.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.