From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: andrew@lunn.ch, alexandre.belloni@bootlin.com, idosch@idosch.org,
ioana.ciornei@nxp.com, kabel@blackhole.sk, f.fainelli@gmail.com,
davem@davemloft.net, Steen.Hegelund@microchip.com,
bridge@lists.linux-foundation.org, nikolay@nvidia.com,
roopa@nvidia.com, kuba@kernel.org, vivien.didelot@gmail.com,
grygorii.strashko@ti.com, jiri@resnulli.us, vkochan@marvell.com,
dqfext@gmail.com, claudiu.manoil@nxp.com,
lars.povlsen@microchip.com, netdev@vger.kernel.org,
UNGLinuxDriver@microchip.com, tchornyi@marvell.com,
tobias@waldekranz.com
Subject: Re: [Bridge] [PATCH v5 net-next 0/5] Allow TX forwarding for the software bridge data path to be offloaded to capable devices
Date: Fri, 23 Jul 2021 15:50:05 +0000 [thread overview]
Message-ID: <162705540587.23511.775470565736247308.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210722155542.2897921-1-vladimir.oltean@nxp.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Thu, 22 Jul 2021 18:55:37 +0300 you wrote:
> On RX, switchdev drivers have the ability to mark packets for the
> software bridge as "already forwarded in hardware" via
> skb->offload_fwd_mark. This instructs the nbp_switchdev_allowed_egress()
> function to perform software forwarding of that packet only to the bridge
> ports that are not in the same hardware domain as the source packet.
>
> This series expands the concept for TX, in the sense that we can trust
> the accelerator to:
> (a) look up its FDB (which is more or less in sync with the software
> bridge FDB) for selecting the destination ports for a packet
> (b) replicate the frame in hardware in case it's a multicast/broadcast,
> instead of the software bridge having to clone it and send the
> clones to each net device one at a time. This reduces the bandwidth
> needed between the CPU and the accelerator, as well as the CPU time
> spent.
>
> [...]
Here is the summary with links:
- [v5,net-next,1/5] net: bridge: switchdev: allow the TX data plane forwarding to be offloaded
https://git.kernel.org/netdev/net-next/c/472111920f1c
- [v5,net-next,2/5] net: dsa: track the number of switches in a tree
https://git.kernel.org/netdev/net-next/c/5b22d3669f2f
- [v5,net-next,3/5] net: dsa: add support for bridge TX forwarding offload
https://git.kernel.org/netdev/net-next/c/123abc06e74f
- [v5,net-next,4/5] net: dsa: mv88e6xxx: map virtual bridges with forwarding offload in the PVT
https://git.kernel.org/netdev/net-next/c/ce5df6894a57
- [v5,net-next,5/5] net: dsa: tag_dsa: offload the bridge forwarding process
https://git.kernel.org/netdev/net-next/c/d82f8ab0d874
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, davem@davemloft.net,
andrew@lunn.ch, f.fainelli@gmail.com, vivien.didelot@gmail.com,
jiri@resnulli.us, idosch@idosch.org, tobias@waldekranz.com,
roopa@nvidia.com, nikolay@nvidia.com, stephen@networkplumber.org,
bridge@lists.linux-foundation.org, grygorii.strashko@ti.com,
kabel@blackhole.sk, dqfext@gmail.com, vkochan@marvell.com,
tchornyi@marvell.com, ioana.ciornei@nxp.com,
lars.povlsen@microchip.com, Steen.Hegelund@microchip.com,
UNGLinuxDriver@microchip.com, claudiu.manoil@nxp.com,
alexandre.belloni@bootlin.com
Subject: Re: [PATCH v5 net-next 0/5] Allow TX forwarding for the software bridge data path to be offloaded to capable devices
Date: Fri, 23 Jul 2021 15:50:05 +0000 [thread overview]
Message-ID: <162705540587.23511.775470565736247308.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210722155542.2897921-1-vladimir.oltean@nxp.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Thu, 22 Jul 2021 18:55:37 +0300 you wrote:
> On RX, switchdev drivers have the ability to mark packets for the
> software bridge as "already forwarded in hardware" via
> skb->offload_fwd_mark. This instructs the nbp_switchdev_allowed_egress()
> function to perform software forwarding of that packet only to the bridge
> ports that are not in the same hardware domain as the source packet.
>
> This series expands the concept for TX, in the sense that we can trust
> the accelerator to:
> (a) look up its FDB (which is more or less in sync with the software
> bridge FDB) for selecting the destination ports for a packet
> (b) replicate the frame in hardware in case it's a multicast/broadcast,
> instead of the software bridge having to clone it and send the
> clones to each net device one at a time. This reduces the bandwidth
> needed between the CPU and the accelerator, as well as the CPU time
> spent.
>
> [...]
Here is the summary with links:
- [v5,net-next,1/5] net: bridge: switchdev: allow the TX data plane forwarding to be offloaded
https://git.kernel.org/netdev/net-next/c/472111920f1c
- [v5,net-next,2/5] net: dsa: track the number of switches in a tree
https://git.kernel.org/netdev/net-next/c/5b22d3669f2f
- [v5,net-next,3/5] net: dsa: add support for bridge TX forwarding offload
https://git.kernel.org/netdev/net-next/c/123abc06e74f
- [v5,net-next,4/5] net: dsa: mv88e6xxx: map virtual bridges with forwarding offload in the PVT
https://git.kernel.org/netdev/net-next/c/ce5df6894a57
- [v5,net-next,5/5] net: dsa: tag_dsa: offload the bridge forwarding process
https://git.kernel.org/netdev/net-next/c/d82f8ab0d874
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-07-23 15:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 15:55 [Bridge] [PATCH v5 net-next 0/5] Allow TX forwarding for the software bridge data path to be offloaded to capable devices Vladimir Oltean
2021-07-22 15:55 ` Vladimir Oltean
2021-07-22 15:55 ` [Bridge] [PATCH v5 net-next 1/5] net: bridge: switchdev: allow the TX data plane forwarding to be offloaded Vladimir Oltean
2021-07-22 15:55 ` Vladimir Oltean
2021-07-22 15:55 ` [Bridge] [PATCH v5 net-next 2/5] net: dsa: track the number of switches in a tree Vladimir Oltean
2021-07-22 15:55 ` Vladimir Oltean
2021-07-22 15:55 ` [Bridge] [PATCH v5 net-next 3/5] net: dsa: add support for bridge TX forwarding offload Vladimir Oltean
2021-07-22 15:55 ` Vladimir Oltean
2021-07-22 15:55 ` [Bridge] [PATCH v5 net-next 4/5] net: dsa: mv88e6xxx: map virtual bridges with forwarding offload in the PVT Vladimir Oltean
2021-07-22 15:55 ` Vladimir Oltean
2021-07-22 15:55 ` [Bridge] [PATCH v5 net-next 5/5] net: dsa: tag_dsa: offload the bridge forwarding process Vladimir Oltean
2021-07-22 15:55 ` Vladimir Oltean
2021-07-23 15:50 ` patchwork-bot+netdevbpf [this message]
2021-07-23 15:50 ` [PATCH v5 net-next 0/5] Allow TX forwarding for the software bridge data path to be offloaded to capable devices 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=162705540587.23511.775470565736247308.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=bridge@lists.linux-foundation.org \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=dqfext@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=grygorii.strashko@ti.com \
--cc=idosch@idosch.org \
--cc=ioana.ciornei@nxp.com \
--cc=jiri@resnulli.us \
--cc=kabel@blackhole.sk \
--cc=kuba@kernel.org \
--cc=lars.povlsen@microchip.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--cc=roopa@nvidia.com \
--cc=tchornyi@marvell.com \
--cc=tobias@waldekranz.com \
--cc=vivien.didelot@gmail.com \
--cc=vkochan@marvell.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 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.