From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Nikolay Aleksandrov <nikolay@nvidia.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Florian Fainelli <f.fainelli@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
Roopa Prabhu <roopa@nvidia.com>, Jiri Pirko <jiri@nvidia.com>,
Ido Schimmel <idosch@nvidia.com>,
Rafael Richter <rafael.richter@gin.de>,
Daniel Klauer <daniel.klauer@gin.de>,
Tobias Waldekranz <tobias@waldekranz.com>
Subject: Re: [PATCH v2 net-next 1/8] net: bridge: vlan: notify switchdev only when something changed
Date: Tue, 15 Feb 2022 14:36:23 +0000 [thread overview]
Message-ID: <20220215143623.wg436nxsr3yxj7as@skbuf> (raw)
In-Reply-To: <5db82bf1-844d-0709-c85e-cbe62445e7dc@nvidia.com>
On Tue, Feb 15, 2022 at 01:08:13PM +0200, Nikolay Aleksandrov wrote:
> On 15/02/2022 12:30, Vladimir Oltean wrote:
> > On Tue, Feb 15, 2022 at 12:12:11PM +0200, Nikolay Aleksandrov wrote:
> >> On 15/02/2022 11:54, Vladimir Oltean wrote:
> >>> On Tue, Feb 15, 2022 at 10:54:26AM +0200, Nikolay Aleksandrov wrote:
> >>>>> +/* return true if anything will change as a result of __vlan_add_flags,
> >>>>> + * false otherwise
> >>>>> + */
> >>>>> +static bool __vlan_flags_would_change(struct net_bridge_vlan *v, u16 flags)
> >>>>> +{
> >>>>> + struct net_bridge_vlan_group *vg;
> >>>>> + u16 old_flags = v->flags;
> >>>>> + bool pvid_changed;
> >>>>>
> >>>>> - return ret || !!(old_flags ^ v->flags);
> >>>>> + if (br_vlan_is_master(v))
> >>>>> + vg = br_vlan_group(v->br);
> >>>>> + else
> >>>>> + vg = nbp_vlan_group(v->port);
> >>>>> +
> >>>>> + if (flags & BRIDGE_VLAN_INFO_PVID)
> >>>>> + pvid_changed = (vg->pvid == v->vid);
> >>>>> + else
> >>>>> + pvid_changed = (vg->pvid != v->vid);
> >>>>> +
> >>>>> + return pvid_changed || !!(old_flags ^ v->flags);
> >>>>> }
> >>>>
> >>>> These two have to depend on each other, otherwise it's error-prone and
> >>>> surely in the future someone will forget to update both.
> >>>> How about add a "commit" argument to __vlan_add_flags and possibly rename
> >>>> it to __vlan_update_flags, then add 2 small helpers like __vlan_update_flags_precommit
> >>>> with commit == false and __vlan_update_flags_commit with commit == true.
> >>>> Or some other naming, the point is to always use the same flow and checks
> >>>> when updating the flags to make sure people don't forget.
> >>>
> >>> You want to squash __vlan_flags_would_change() and __vlan_add_flags()
> >>> into a single function? But "would_change" returns bool, and "add"
> >>> returns void.
> >>>
> >>
> >> Hence the wrappers for commit == false and commit == true. You could name the precommit
> >> one __vlan_flags_would_change or something more appropriate. The point is to make
> >> sure we always update both when flags are changed.
> >
> > I still have a little doubt that I understood you properly.
> > Do you mean like this?
> >
>
> By the way I just noticed that __vlan_flags_would_change has another bug, it's testing
> vlan's flags against themselves without any change (old_flags == v->flags).
Yes, I think I noticed that too when I put some debugging prints, I
wasn't sure where it came from though.
> I meant something similar to this (quickly hacked, untested, add flags probably
> could be renamed to something more appropriate):
>
> diff --git a/net/bridge/br_vlan.c b/net/bridge/br_vlan.c
> index 1402d5ca242d..1de69090d3cb 100644
> --- a/net/bridge/br_vlan.c
> +++ b/net/bridge/br_vlan.c
> @@ -34,53 +34,66 @@ static struct net_bridge_vlan *br_vlan_lookup(struct rhashtable *tbl, u16 vid)
> return rhashtable_lookup_fast(tbl, &vid, br_vlan_rht_params);
> }
>
> -static bool __vlan_add_pvid(struct net_bridge_vlan_group *vg,
> +static void __vlan_add_pvid(struct net_bridge_vlan_group *vg,
> const struct net_bridge_vlan *v)
> {
> if (vg->pvid == v->vid)
> - return false;
> + return;
>
> smp_wmb();
> br_vlan_set_pvid_state(vg, v->state);
> vg->pvid = v->vid;
> -
> - return true;
> }
>
> -static bool __vlan_delete_pvid(struct net_bridge_vlan_group *vg, u16 vid)
> +static void __vlan_delete_pvid(struct net_bridge_vlan_group *vg, u16 vid)
> {
> if (vg->pvid != vid)
> - return false;
> + return;
>
> smp_wmb();
> vg->pvid = 0;
> -
> - return true;
> }
>
> /* return true if anything changed, false otherwise */
> -static bool __vlan_add_flags(struct net_bridge_vlan *v, u16 flags)
> +static bool __vlan_add_flags(struct net_bridge_vlan *v, u16 flags, bool commit)
> {
> struct net_bridge_vlan_group *vg;
> - u16 old_flags = v->flags;
> - bool ret;
> + bool change;
>
> if (br_vlan_is_master(v))
> vg = br_vlan_group(v->br);
> else
> vg = nbp_vlan_group(v->port);
>
> + /* check if anything would be changed on commit */
> + change = (!!(flags & BRIDGE_VLAN_INFO_PVID) == !!(vg->pvid != v->vid) ||
> + ((flags ^ v->flags) & BRIDGE_VLAN_INFO_UNTAGGED));
> +
> + if (!commit)
> + goto out;
> +
> if (flags & BRIDGE_VLAN_INFO_PVID)
> - ret = __vlan_add_pvid(vg, v);
> + __vlan_add_pvid(vg, v);
> else
> - ret = __vlan_delete_pvid(vg, v->vid);
> + __vlan_delete_pvid(vg, v->vid);
>
> if (flags & BRIDGE_VLAN_INFO_UNTAGGED)
> v->flags |= BRIDGE_VLAN_INFO_UNTAGGED;
> else
> v->flags &= ~BRIDGE_VLAN_INFO_UNTAGGED;
>
> - return ret || !!(old_flags ^ v->flags);
> +out:
> + return change;
> +}
> +
> +static bool __vlan_flags_would_change(struct net_bridge_vlan *v, u16 flags)
> +{
> + return __vlan_add_flags(v, flags, false);
> +}
> +
> +static bool __vlan_flags_commit(struct net_bridge_vlan *v, u16 flags)
> +{
> + return __vlan_add_flags(v, flags, true);
> }
>
> static int __vlan_vid_add(struct net_device *dev, struct net_bridge *br,
Ah, ok, now I understand what you mean. I'll integrate this, retest and
prepare a v3 if there are no other objections. Thanks!
next prev parent reply other threads:[~2022-02-15 14:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 23:31 [PATCH v2 net-next 0/8] Replay and offload host VLAN entries in DSA Vladimir Oltean
2022-02-14 23:31 ` [PATCH v2 net-next 1/8] net: bridge: vlan: notify switchdev only when something changed Vladimir Oltean
2022-02-15 0:05 ` Vladimir Oltean
2022-02-15 8:54 ` Nikolay Aleksandrov
2022-02-15 9:54 ` Vladimir Oltean
2022-02-15 10:10 ` Vladimir Oltean
2022-02-15 10:15 ` Nikolay Aleksandrov
2022-02-15 10:12 ` Nikolay Aleksandrov
2022-02-15 10:30 ` Vladimir Oltean
2022-02-15 11:08 ` Nikolay Aleksandrov
2022-02-15 11:10 ` Nikolay Aleksandrov
2022-02-15 14:36 ` Vladimir Oltean [this message]
2022-02-15 15:38 ` Vladimir Oltean
2022-02-15 15:44 ` Nikolay Aleksandrov
2022-02-15 15:52 ` Vladimir Oltean
2022-02-14 23:31 ` [PATCH v2 net-next 2/8] net: bridge: switchdev: differentiate new VLANs from changed ones Vladimir Oltean
2022-02-14 23:31 ` [PATCH v2 net-next 3/8] net: bridge: make nbp_switchdev_unsync_objs() follow reverse order of sync() Vladimir Oltean
2022-02-14 23:31 ` [PATCH v2 net-next 4/8] net: bridge: switchdev: replay all VLAN groups Vladimir Oltean
2022-02-14 23:31 ` [PATCH v2 net-next 5/8] net: switchdev: rename switchdev_lower_dev_find to switchdev_lower_dev_find_rcu Vladimir Oltean
2022-02-14 23:31 ` [PATCH v2 net-next 6/8] net: switchdev: introduce switchdev_handle_port_obj_{add,del} for foreign interfaces Vladimir Oltean
2022-02-14 23:31 ` [PATCH v2 net-next 7/8] net: dsa: add explicit support for host bridge VLANs Vladimir Oltean
2022-02-14 23:31 ` [PATCH v2 net-next 8/8] net: dsa: offload bridge port VLANs on foreign interfaces Vladimir Oltean
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=20220215143623.wg436nxsr3yxj7as@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=andrew@lunn.ch \
--cc=daniel.klauer@gin.de \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=idosch@nvidia.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--cc=olteanv@gmail.com \
--cc=rafael.richter@gin.de \
--cc=roopa@nvidia.com \
--cc=tobias@waldekranz.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