From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: Casper Andersson <casper.casan@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Lars Povlsen <lars.povlsen@microchip.com>,
Steen Hegelund <Steen.Hegelund@microchip.com>,
<UNGLinuxDriver@microchip.com>, <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next v2] net: sparx5: Support offloading of bridge port flooding flags
Date: Tue, 22 Feb 2022 19:08:54 +0100 [thread overview]
Message-ID: <20220222180854.ah3klvdgffpmk26n@soft-dev3-1.localhost> (raw)
In-Reply-To: <20220222143525.ubtovkknjxfiflij@wse-c0155>
The 02/22/2022 15:35, Casper Andersson wrote:
> [Some people who received this message don't often get email from casper.casan@gmail.com. Learn why this is important at http://aka.ms/LearnAboutSenderIdentification.]
>
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> Though the SparX-5i can control IPv4/6 multicasts separately from non-IP
> multicasts, these are all muxed onto the bridge's BR_MCAST_FLOOD flag.
>
> Signed-off-by: Casper Andersson <casper.casan@gmail.com>
Reviewed-by: Horatiu Vultur <horatiu.vultur@microchip.com>
> ---
> Since Protonmail apparently caused issues with certain email clients
> I have now switched to using gmail. Hopefully, there will be no issues
> this time.
>
> Changes in v2:
> - Added SWITCHDEV_ATTR_ID_PORT_PRE_BRIDGE_FLAGS callback
>
> .../microchip/sparx5/sparx5_switchdev.c | 21 ++++++++++++++++++-
> 1 file changed, 20 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/microchip/sparx5/sparx5_switchdev.c b/drivers/net/ethernet/microchip/sparx5/sparx5_switchdev.c
> index 649ca609884a..dc79791201d8 100644
> --- a/drivers/net/ethernet/microchip/sparx5/sparx5_switchdev.c
> +++ b/drivers/net/ethernet/microchip/sparx5/sparx5_switchdev.c
> @@ -19,11 +19,27 @@ struct sparx5_switchdev_event_work {
> unsigned long event;
> };
>
> +static int sparx5_port_attr_pre_bridge_flags(struct sparx5_port *port,
> + struct switchdev_brport_flags flags)
> +{
> + if (flags.mask & ~(BR_FLOOD | BR_MCAST_FLOOD | BR_BCAST_FLOOD))
> + return -EINVAL;
> +
> + return 0;
> +}
> +
> static void sparx5_port_attr_bridge_flags(struct sparx5_port *port,
> struct switchdev_brport_flags flags)
> {
> + int pgid;
> +
> if (flags.mask & BR_MCAST_FLOOD)
> - sparx5_pgid_update_mask(port, PGID_MC_FLOOD, true);
> + for (pgid = PGID_MC_FLOOD; pgid <= PGID_IPV6_MC_CTRL; pgid++)
> + sparx5_pgid_update_mask(port, pgid, !!(flags.val & BR_MCAST_FLOOD));
> + if (flags.mask & BR_FLOOD)
> + sparx5_pgid_update_mask(port, PGID_UC_FLOOD, !!(flags.val & BR_FLOOD));
> + if (flags.mask & BR_BCAST_FLOOD)
> + sparx5_pgid_update_mask(port, PGID_BCAST, !!(flags.val & BR_BCAST_FLOOD));
> }
>
> static void sparx5_attr_stp_state_set(struct sparx5_port *port,
> @@ -72,6 +88,9 @@ static int sparx5_port_attr_set(struct net_device *dev, const void *ctx,
> struct sparx5_port *port = netdev_priv(dev);
>
> switch (attr->id) {
> + case SWITCHDEV_ATTR_ID_PORT_PRE_BRIDGE_FLAGS:
> + return sparx5_port_attr_pre_bridge_flags(port,
> + attr->u.brport_flags);
> case SWITCHDEV_ATTR_ID_PORT_BRIDGE_FLAGS:
> sparx5_port_attr_bridge_flags(port, attr->u.brport_flags);
> break;
> --
> 2.30.2
>
--
/Horatiu
next prev parent reply other threads:[~2022-02-22 18:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 14:35 [PATCH net-next v2] net: sparx5: Support offloading of bridge port flooding flags Casper Andersson
2022-02-22 18:08 ` Horatiu Vultur [this message]
2022-02-22 23:47 ` Jakub Kicinski
2022-02-23 0:06 ` Jakub Kicinski
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=20220222180854.ah3klvdgffpmk26n@soft-dev3-1.localhost \
--to=horatiu.vultur@microchip.com \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=casper.casan@gmail.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=lars.povlsen@microchip.com \
--cc=netdev@vger.kernel.org \
/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