From: patchwork-bot+netdevbpf@kernel.org
To: Oleksandr Mazur <oleksandr.mazur@plvision.eu>
Cc: roopa@nvidia.com, razor@blackwall.org, davem@davemloft.net,
kuba@kernel.org, ivecera@redhat.com, yotamg@mellanox.com,
nogahf@mellanox.com, jiri@mellanox.com,
taras.chornyi@plvision.eu, volodymyr.mytnyk@plvision.eu,
mickeyr@marvell.com, nikolay@nvidia.com,
bridge@lists.linux-foundation.org, vladimir.oltean@nxp.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] net: bridge: multicast: notify switchdev driver whenever MC processing gets disabled
Date: Thu, 17 Feb 2022 04:40:09 +0000 [thread overview]
Message-ID: <164507280928.19778.1810833319273321601.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220215165303.31908-1-oleksandr.mazur@plvision.eu>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 15 Feb 2022 18:53:03 +0200 you wrote:
> Whenever bridge driver hits the max capacity of MDBs, it disables
> the MC processing (by setting corresponding bridge option), but never
> notifies switchdev about such change (the notifiers are called only upon
> explicit setting of this option, through the registered netlink interface).
>
> This could lead to situation when Software MDB processing gets disabled,
> but this event never gets offloaded to the underlying Hardware.
>
> [...]
Here is the summary with links:
- [net,v2] net: bridge: multicast: notify switchdev driver whenever MC processing gets disabled
https://git.kernel.org/netdev/net/c/c832962ac972
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:[~2022-02-17 4:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 16:53 [PATCH net v2] net: bridge: multicast: notify switchdev driver whenever MC processing gets disabled Oleksandr Mazur
2022-02-15 16:56 ` Nikolay Aleksandrov
2022-02-17 4:40 ` 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=164507280928.19778.1810833319273321601.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=ivecera@redhat.com \
--cc=jiri@mellanox.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mickeyr@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--cc=nogahf@mellanox.com \
--cc=oleksandr.mazur@plvision.eu \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.com \
--cc=taras.chornyi@plvision.eu \
--cc=vladimir.oltean@nxp.com \
--cc=volodymyr.mytnyk@plvision.eu \
--cc=yotamg@mellanox.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;
as well as URLs for NNTP newsgroup(s).