From: Florian Fainelli <f.fainelli@gmail.com>
To: Vladimir Oltean <vladimir.oltean@nxp.com>,
netdev@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>
Cc: Andrew Lunn <andrew@lunn.ch>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Jiri Pirko <jiri@resnulli.us>, DENG Qingfang <dqfext@gmail.com>,
bridge@lists.linux-foundation.org,
Ido Schimmel <idosch@idosch.org>,
Nikolay Aleksandrov <nikolay@nvidia.com>,
Roopa Prabhu <roopa@nvidia.com>, Marek Behun <kabel@blackhole.sk>,
Vivien Didelot <vivien.didelot@gmail.com>,
Tobias Waldekranz <tobias@waldekranz.com>
Subject: Re: [Bridge] [PATCH v4 net-next 11/15] net: bridge: switchdev: allow the TX data plane forwarding to be offloaded
Date: Sun, 18 Jul 2021 19:43:23 -0700 [thread overview]
Message-ID: <d81cf0d4-3680-8f87-63ba-d2d843394d5b@gmail.com> (raw)
In-Reply-To: <20210718214434.3938850-12-vladimir.oltean@nxp.com>
On 7/18/2021 2:44 PM, Vladimir Oltean wrote:
> From: Tobias Waldekranz <tobias@waldekranz.com>
>
> Allow switchdevs to forward frames from the CPU in accordance with the
> bridge configuration in the same way as is done between bridge
> ports. This means that the bridge will only send a single skb towards
> one of the ports under the switchdev's control, and expects the driver
> to deliver the packet to all eligible ports in its domain.
>
> Primarily this improves the performance of multicast flows with
> multiple subscribers, as it allows the hardware to perform the frame
> replication.
>
> The basic flow between the driver and the bridge is as follows:
>
> - When joining a bridge port, the switchdev driver calls
> switchdev_bridge_port_offload() with tx_fwd_offload = true.
>
> - The bridge sends offloadable skbs to one of the ports under the
> switchdev's control using skb->offload_fwd_mark = true.
>
> - The switchdev driver checks the skb->offload_fwd_mark field and lets
> its FDB lookup select the destination port mask for this packet.
>
> v1->v2:
> - convert br_input_skb_cb::fwd_hwdoms to a plain unsigned long
> - introduce a static key "br_switchdev_fwd_offload_used" to minimize the
> impact of the newly introduced feature on all the setups which don't
> have hardware that can make use of it
> - introduce a check for nbp->flags & BR_FWD_OFFLOAD to optimize cache
> line access
> - reorder nbp_switchdev_frame_mark_accel() and br_handle_vlan() in
> __br_forward()
> - do not strip VLAN on egress if forwarding offload on VLAN-aware bridge
> is being used
> - propagate errors from .ndo_dfwd_add_station() if not EOPNOTSUPP
>
> v2->v3:
> - replace the solution based on .ndo_dfwd_add_station with a solution
> based on switchdev_bridge_port_offload
> - rename BR_FWD_OFFLOAD to BR_TX_FWD_OFFLOAD
> v3->v4: rebase
>
> Signed-off-by: Tobias Waldekranz <tobias@waldekranz.com>
> Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
--
Florian
next prev parent reply other threads:[~2021-07-19 2:43 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-18 21:44 [Bridge] [PATCH v4 net-next 00/15] Allow forwarding for the software bridge data path to be offloaded to capable devices Vladimir Oltean
2021-07-18 21:44 ` [Bridge] [PATCH v4 net-next 01/15] net: dpaa2-switch: use extack in dpaa2_switch_port_bridge_join Vladimir Oltean
2021-07-19 9:17 ` Ioana Ciornei
2021-07-18 21:44 ` [Bridge] [PATCH v4 net-next 02/15] net: dpaa2-switch: refactor prechangeupper sanity checks Vladimir Oltean
2021-07-19 9:18 ` Ioana Ciornei
2021-07-18 21:44 ` [Bridge] [PATCH v4 net-next 03/15] mlxsw: spectrum: " Vladimir Oltean
2021-07-18 21:44 ` [Bridge] [PATCH v4 net-next 04/15] mlxsw: spectrum: refactor leaving an 8021q upper that is a bridge port Vladimir Oltean
2021-07-19 2:16 ` Florian Fainelli
2021-07-18 21:44 ` [Bridge] [PATCH v4 net-next 05/15] net: marvell: prestera: refactor prechangeupper sanity checks Vladimir Oltean
2021-07-19 2:20 ` Florian Fainelli
2021-07-18 21:44 ` [Bridge] [PATCH v4 net-next 06/15] net: switchdev: guard drivers against multiple obj replays on same bridge port Vladimir Oltean
2021-07-19 2:17 ` Florian Fainelli
2021-07-18 21:44 ` [Bridge] [PATCH v4 net-next 07/15] net: bridge: disambiguate offload_fwd_mark Vladimir Oltean
2021-07-19 2:26 ` Florian Fainelli
2021-07-18 21:44 ` [Bridge] [PATCH v4 net-next 08/15] net: bridge: switchdev: recycle unused hwdoms Vladimir Oltean
2021-07-18 21:44 ` [Bridge] [PATCH v4 net-next 09/15] net: bridge: switchdev: let drivers inform which bridge ports are offloaded Vladimir Oltean
2021-07-19 9:23 ` Ioana Ciornei
2021-07-20 7:53 ` Horatiu Vultur
2021-07-20 8:45 ` Vladimir Oltean
2021-07-18 21:44 ` [Bridge] [PATCH v4 net-next 10/15] net: bridge: switchdev object replay helpers for everybody Vladimir Oltean
2021-07-19 8:19 ` Vladimir Oltean
2021-07-19 9:26 ` Ioana Ciornei
2021-07-18 21:44 ` [Bridge] [PATCH v4 net-next 11/15] net: bridge: switchdev: allow the TX data plane forwarding to be offloaded Vladimir Oltean
2021-07-19 2:43 ` Florian Fainelli [this message]
2021-07-19 7:22 ` Vladimir Oltean
2021-07-18 21:44 ` [Bridge] [PATCH v4 net-next 12/15] net: dsa: track the number of switches in a tree Vladimir Oltean
2021-07-19 2:54 ` Florian Fainelli
2021-07-18 21:44 ` [Bridge] [PATCH v4 net-next 13/15] net: dsa: add support for bridge TX forwarding offload Vladimir Oltean
2021-07-19 2:51 ` Florian Fainelli
2021-07-18 21:44 ` [Bridge] [PATCH v4 net-next 14/15] net: dsa: mv88e6xxx: map virtual bridges with forwarding offload in the PVT Vladimir Oltean
2021-07-19 2:52 ` Florian Fainelli
2021-07-18 21:44 ` [Bridge] [PATCH v4 net-next 15/15] net: dsa: tag_dsa: offload the bridge forwarding process Vladimir Oltean
2021-07-19 2:47 ` Florian Fainelli
2021-07-19 7:41 ` Vladimir Oltean
2021-07-20 11:24 ` [Bridge] [PATCH v4 net-next 00/15] Allow forwarding for the software bridge data path to be offloaded to capable devices Ido Schimmel
2021-07-20 13:20 ` Vladimir Oltean
2021-07-20 13:51 ` Ido Schimmel
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=d81cf0d4-3680-8f87-63ba-d2d843394d5b@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=dqfext@gmail.com \
--cc=grygorii.strashko@ti.com \
--cc=idosch@idosch.org \
--cc=jiri@resnulli.us \
--cc=kabel@blackhole.sk \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--cc=roopa@nvidia.com \
--cc=tobias@waldekranz.com \
--cc=vivien.didelot@gmail.com \
--cc=vladimir.oltean@nxp.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