From: Tobias Waldekranz <tobias@waldekranz.com>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org,
Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Jiri Pirko <jiri@resnulli.us>, Ivan Vecera <ivecera@redhat.com>,
Roopa Prabhu <roopa@nvidia.com>,
Nikolay Aleksandrov <razor@blackwall.org>,
Russell King <linux@armlinux.org.uk>,
Petr Machata <petrm@nvidia.com>, Ido Schimmel <idosch@nvidia.com>,
Matt Johnston <matt@codeconstruct.com.au>,
Cooper Lees <me@cooperlees.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
bridge@lists.linux-foundation.org
Subject: Re: [PATCH v4 net-next 10/15] net: dsa: Validate hardware support for MST
Date: Wed, 16 Mar 2022 10:15:18 +0100 [thread overview]
Message-ID: <8735jil0m1.fsf@waldekranz.com> (raw)
In-Reply-To: <20220315171108.ameddbqv2sehq3pp@skbuf>
On Tue, Mar 15, 2022 at 19:11, Vladimir Oltean <olteanv@gmail.com> wrote:
> On Tue, Mar 15, 2022 at 01:25:38AM +0100, Tobias Waldekranz wrote:
>> When joining a bridge where MST is enabled, we validate that the
>> proper offloading support is in place, otherwise we fallback to
>> software bridging.
>>
>> When then mode is changed on a bridge in which we are members, we
>> refuse the change if offloading is not supported.
>>
>> At the moment we only check for configurable learning, but this will
>> be further restricted as we support more MST related switchdev events.
>>
>> Signed-off-by: Tobias Waldekranz <tobias@waldekranz.com>
>> ---
>> net/dsa/dsa_priv.h | 2 ++
>> net/dsa/port.c | 22 ++++++++++++++++++++++
>> net/dsa/slave.c | 6 ++++++
>> 3 files changed, 30 insertions(+)
>>
>> diff --git a/net/dsa/dsa_priv.h b/net/dsa/dsa_priv.h
>> index f20bdd8ea0a8..2aba420696ef 100644
>> --- a/net/dsa/dsa_priv.h
>> +++ b/net/dsa/dsa_priv.h
>> @@ -234,6 +234,8 @@ int dsa_port_vlan_filtering(struct dsa_port *dp, bool vlan_filtering,
>> struct netlink_ext_ack *extack);
>> bool dsa_port_skip_vlan_configuration(struct dsa_port *dp);
>> int dsa_port_ageing_time(struct dsa_port *dp, clock_t ageing_clock);
>> +int dsa_port_mst_enable(struct dsa_port *dp, bool on,
>> + struct netlink_ext_ack *extack);
>> int dsa_port_mtu_change(struct dsa_port *dp, int new_mtu,
>> bool targeted_match);
>> int dsa_port_fdb_add(struct dsa_port *dp, const unsigned char *addr,
>> diff --git a/net/dsa/port.c b/net/dsa/port.c
>> index 58291df14cdb..02214033cec0 100644
>> --- a/net/dsa/port.c
>> +++ b/net/dsa/port.c
>> @@ -321,6 +321,11 @@ static void dsa_port_bridge_destroy(struct dsa_port *dp,
>> kfree(bridge);
>> }
>>
>> +static bool dsa_port_supports_mst(struct dsa_port *dp)
>> +{
>> + return dsa_port_can_configure_learning(dp);
>> +}
>> +
>> int dsa_port_bridge_join(struct dsa_port *dp, struct net_device *br,
>> struct netlink_ext_ack *extack)
>> {
>> @@ -334,6 +339,9 @@ int dsa_port_bridge_join(struct dsa_port *dp, struct net_device *br,
>> struct net_device *brport_dev;
>> int err;
>>
>> + if (br_mst_enabled(br) && !dsa_port_supports_mst(dp))
>> + return -EOPNOTSUPP;
>> +
>> /* Here the interface is already bridged. Reflect the current
>> * configuration so that drivers can program their chips accordingly.
>> */
>> @@ -735,6 +743,20 @@ int dsa_port_ageing_time(struct dsa_port *dp, clock_t ageing_clock)
>> return 0;
>> }
>>
>> +int dsa_port_mst_enable(struct dsa_port *dp, bool on,
>> + struct netlink_ext_ack *extack)
>> +{
>> + if (!on)
>> + return 0;
>> +
>> + if (!dsa_port_supports_mst(dp)) {
>> + NL_SET_ERR_MSG_MOD(extack, "Hardware does not support MST");
>> + return -EINVAL;
>> + }
>> +
>> + return 0;
>> +}
>
> Experimenting a bit... maybe this looks tidier? We make the "if" condition
> have the same basic structure as the previous "if (br_mst_enabled(br) &&
> !dsa_port_supports_mst(dp))", albeit transformed using De Morgan's rules.
>
> {
> if (!on || dsa_port_supports_mst(dp))
> return 0;
>
> NL_SET_ERR_MSG_MOD(extack, "Hardware does not support MST");
> return -EINVAL;
> }
I initially had it like this. It looks tidier, yes - but to me the
intent is less obvious when reading it. How about:
{
if (on && !dsa_port_supports_mst(dp)) {
NL_SET_ERR_MSG_MOD(extack, "Hardware does not support MST");
return -EINVAL;
}
return 0;
}
>> +
>> int dsa_port_pre_bridge_flags(const struct dsa_port *dp,
>> struct switchdev_brport_flags flags,
>> struct netlink_ext_ack *extack)
>> diff --git a/net/dsa/slave.c b/net/dsa/slave.c
>> index 647adee97f7f..879d18cc99cb 100644
>> --- a/net/dsa/slave.c
>> +++ b/net/dsa/slave.c
>> @@ -463,6 +463,12 @@ static int dsa_slave_port_attr_set(struct net_device *dev, const void *ctx,
>>
>> ret = dsa_port_ageing_time(dp, attr->u.ageing_time);
>> break;
>> + case SWITCHDEV_ATTR_ID_BRIDGE_MST:
>> + if (!dsa_port_offloads_bridge_dev(dp, attr->orig_dev))
>> + return -EOPNOTSUPP;
>> +
>> + ret = dsa_port_mst_enable(dp, attr->u.mst, extack);
>> + break;
>> case SWITCHDEV_ATTR_ID_PORT_PRE_BRIDGE_FLAGS:
>> if (!dsa_port_offloads_bridge_port(dp, attr->orig_dev))
>> return -EOPNOTSUPP;
>> --
>> 2.25.1
>>
next prev parent reply other threads:[~2022-03-16 9:15 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 0:25 [PATCH v4 net-next 00/15] net: bridge: Multiple Spanning Trees Tobias Waldekranz
2022-03-15 0:25 ` [PATCH v4 net-next 01/15] net: bridge: mst: Multiple Spanning Tree (MST) mode Tobias Waldekranz
2022-03-15 0:25 ` [PATCH v4 net-next 02/15] net: bridge: mst: Allow changing a VLAN's MSTI Tobias Waldekranz
2022-03-15 0:25 ` [PATCH v4 net-next 03/15] net: bridge: mst: Support setting and reporting MST port states Tobias Waldekranz
2022-03-15 9:52 ` Nikolay Aleksandrov
2022-03-15 16:54 ` Vladimir Oltean
2022-03-15 22:35 ` Tobias Waldekranz
2022-03-15 0:25 ` [PATCH v4 net-next 04/15] net: bridge: mst: Notify switchdev drivers of MST mode changes Tobias Waldekranz
2022-03-15 5:32 ` Jakub Kicinski
2022-03-15 22:28 ` Tobias Waldekranz
2022-03-15 0:25 ` [PATCH v4 net-next 05/15] net: bridge: mst: Notify switchdev drivers of VLAN MSTI migrations Tobias Waldekranz
2022-03-15 0:25 ` [PATCH v4 net-next 06/15] net: bridge: mst: Notify switchdev drivers of MST state changes Tobias Waldekranz
2022-03-15 0:25 ` [PATCH v4 net-next 07/15] net: bridge: mst: Add helper to map an MSTI to a VID set Tobias Waldekranz
2022-03-15 0:25 ` [PATCH v4 net-next 08/15] net: bridge: mst: Add helper to check if MST is enabled Tobias Waldekranz
2022-03-15 0:25 ` [PATCH v4 net-next 09/15] net: dsa: Never offload FDB entries on standalone ports Tobias Waldekranz
2022-03-15 16:33 ` Vladimir Oltean
2022-03-15 22:26 ` Tobias Waldekranz
2022-03-15 22:42 ` Vladimir Oltean
2022-03-15 22:57 ` Tobias Waldekranz
2022-03-15 0:25 ` [PATCH v4 net-next 10/15] net: dsa: Validate hardware support for MST Tobias Waldekranz
2022-03-15 17:11 ` Vladimir Oltean
2022-03-16 9:15 ` Tobias Waldekranz [this message]
2022-03-16 13:03 ` Vladimir Oltean
2022-03-15 0:25 ` [PATCH v4 net-next 11/15] net: dsa: Pass VLAN MSTI migration notifications to driver Tobias Waldekranz
2022-03-15 0:25 ` [PATCH v4 net-next 12/15] net: dsa: Handle MST state changes Tobias Waldekranz
2022-03-15 16:42 ` Vladimir Oltean
2022-03-15 16:44 ` Vladimir Oltean
2022-03-16 9:45 ` Tobias Waldekranz
2022-03-16 9:51 ` Tobias Waldekranz
2022-03-16 13:02 ` Vladimir Oltean
2022-03-15 0:25 ` [PATCH v4 net-next 13/15] net: dsa: mv88e6xxx: Disentangle STU from VTU Tobias Waldekranz
2022-03-15 0:25 ` [PATCH v4 net-next 14/15] net: dsa: mv88e6xxx: Export STU as devlink region Tobias Waldekranz
2022-03-15 0:25 ` [PATCH v4 net-next 15/15] net: dsa: mv88e6xxx: MST Offloading Tobias Waldekranz
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=8735jil0m1.fsf@waldekranz.com \
--to=tobias@waldekranz.com \
--cc=andrew@lunn.ch \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=idosch@nvidia.com \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=matt@codeconstruct.com.au \
--cc=me@cooperlees.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=petrm@nvidia.com \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.com \
--cc=vivien.didelot@gmail.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).