netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: petrm@mellanox.com
Cc: netdev@vger.kernel.org, devel@driverdev.osuosl.org,
	bridge@lists.linux-foundation.org, jiri@mellanox.com,
	idosch@mellanox.com, razvan.stefanescu@nxp.com,
	gregkh@linuxfoundation.org, stephen@networkplumber.org,
	andrew@lunn.ch, vivien.didelot@savoirfairelinux.com,
	f.fainelli@gmail.com, nikolay@cumulusnetworks.com,
	dan.carpenter@oracle.com
Subject: Re: [PATCH net-next v4 0/8] net: bridge: Notify about bridge VLANs
Date: Thu, 31 May 2018 14:14:12 -0400 (EDT)	[thread overview]
Message-ID: <20180531.141412.1289727831618161534.davem@davemloft.net> (raw)
In-Reply-To: <cover.1527641426.git.petrm@mellanox.com>

From: Petr Machata <petrm@mellanox.com>
Date: Wed, 30 May 2018 02:55:34 +0200

> In commit 946a11e7408e ("mlxsw: spectrum_span: Allow bridge for gretap
> mirror"), mlxsw got support for offloading mirror-to-gretap such that
> the underlay packet path involves a bridge. In that case, the offload is
> also influenced by PVID setting of said bridge. However, changes to VLAN
> configuration of the bridge itself do not generate switchdev
> notifications, so there's no mechanism to prod mlxsw to update the
> offload when these settings change.
> 
> In this patchset, the problem is resolved by distributing the switchdev
> notification SWITCHDEV_OBJ_ID_PORT_VLAN also for configuration changes
> on bridge VLANs. Since stacked devices distribute the notification to
> lower devices, such event eventually reaches the driver, which can
> determine whether it's a bridge or port VLAN by inspecting orig_dev.
> 
> To keep things consistent, the newly-distributed notifications observe
> the same protocol as the existing ones: dual prepare/commit, with
> -EOPNOTSUPP indicating lack of support, even though there's currently
> nothing to prepare for and nothing to support. Correspondingly, all
> switchdev drivers have been updated to return -EOPNOTSUPP for bridge
> VLAN notifications.
> 
> In patches #1 and #2, the code base is changed to support the following
> additions: functions br_switchdev_port_vlan_add() and
> br_switchdev_port_vlan_del() are introduced to simplify sending
> notifications; and br_vlan_add_existing() is introduced to later make it
> simpler to add error-handling code for the case of configuring a
> preexisting VLAN on bridge CPU port.
> 
> In patches #3-#6, respectively for mlxsw, rocker, DSA and DPAA2 ethsw,
> the new notifications (which are not enabled yet) are ignored to
> maintain the current behavior.
> 
> In patch #7, the notification is actually enabled.
> 
> In patch #8, mlxsw is changed to update offloads of mirror-to-gre also
> for bridge-related notifications.
 ...

Series applied, thanks.

      parent reply	other threads:[~2018-05-31 18:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-30  0:55 [PATCH net-next v4 0/8] net: bridge: Notify about bridge VLANs Petr Machata
2018-05-30  0:56 ` [PATCH net-next v4 1/8] net: bridge: Extract boilerplate around switchdev_port_obj_*() Petr Machata
2018-05-30 15:12   ` Nikolay Aleksandrov
2018-05-30  0:56 ` [PATCH net-next v4 2/8] net: bridge: Extract br_vlan_add_existing() Petr Machata
2018-05-30 15:15   ` Nikolay Aleksandrov
2018-05-30  0:57 ` [PATCH net-next v4 3/8] mlxsw: spectrum_switchdev: Ignore bridge VLAN events Petr Machata
2018-05-30  0:58 ` [PATCH net-next v4 4/8] rocker: rocker_main: " Petr Machata
2018-05-30  0:59 ` [PATCH net-next v4 5/8] dsa: port: " Petr Machata
2018-05-30  2:13   ` Florian Fainelli
2018-05-30  1:00 ` [PATCH net-next v4 6/8] staging: fsl-dpaa2: ethsw: " Petr Machata
2018-05-30  1:00 ` [PATCH net-next v4 7/8] net: bridge: Notify about bridge VLANs Petr Machata
2018-05-30 15:58   ` Nikolay Aleksandrov
2018-05-30  1:00 ` [PATCH net-next v4 8/8] mlxsw: spectrum_switchdev: Schedule respin during trans prepare Petr Machata
2018-05-31 18:14 ` David Miller [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=20180531.141412.1289727831618161534.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=andrew@lunn.ch \
    --cc=bridge@lists.linux-foundation.org \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=idosch@mellanox.com \
    --cc=jiri@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=nikolay@cumulusnetworks.com \
    --cc=petrm@mellanox.com \
    --cc=razvan.stefanescu@nxp.com \
    --cc=stephen@networkplumber.org \
    --cc=vivien.didelot@savoirfairelinux.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).