From: David Miller <davem@davemloft.net>
To: petrm@mellanox.com
Cc: devel@driverdev.osuosl.org, ivecera@redhat.com,
alexandre.belloni@bootlin.com, f.fainelli@gmail.com,
gregkh@linuxfoundation.org, netdev@vger.kernel.org,
vivien.didelot@savoirfairelinux.com, idosch@mellanox.com,
jiri@mellanox.com, andrew@lunn.ch, ioana.ciornei@nxp.com
Subject: Re: [PATCH net-next 00/12] switchdev: Convert switchdev_port_obj_{add,del}() to notifiers
Date: Fri, 23 Nov 2018 18:02:44 -0800 (PST) [thread overview]
Message-ID: <20181123.180244.2269656658446733343.davem@davemloft.net> (raw)
In-Reply-To: <cover.1542927590.git.petrm@mellanox.com>
From: Petr Machata <petrm@mellanox.com>
Date: Thu, 22 Nov 2018 23:27:52 +0000
> An offloading driver may need to have access to switchdev events on
> ports that aren't directly under its control. An example is a VXLAN port
> attached to a bridge offloaded by a driver. The driver needs to know
> about VLANs configured on the VXLAN device. However the VXLAN device
> isn't stashed between the bridge and a front-panel-port device (such as
> is the case e.g. for LAG devices), so the usual switchdev ops don't
> reach the driver.
>
> VXLAN is likely not the only device type like this: in theory any L2
> tunnel device that needs offloading will prompt requirement of this
> sort.
>
> A way to fix this is to give up the notion of port object addition /
> deletion as a switchdev operation, which assumes somewhat tight coupling
> between the message producer and consumer. And instead send the message
> over a notifier chain.
...
Series applied, thank you.
prev parent reply other threads:[~2018-11-24 2:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 23:27 [PATCH net-next 00/12] switchdev: Convert switchdev_port_obj_{add,del}() to notifiers Petr Machata
2018-11-22 23:28 ` [PATCH net-next 01/12] switchdev: SWITCHDEV_OBJ_PORT_{VLAN, MDB}(): Sanitize Petr Machata
2018-11-22 23:28 ` [PATCH net-next 02/12] switchdev: Add a blocking notifier chain Petr Machata
2018-11-22 23:28 ` [PATCH net-next 03/12] switchdev: Add SWITCHDEV_PORT_OBJ_ADD, SWITCHDEV_PORT_OBJ_DEL Petr Machata
2018-11-22 23:28 ` [PATCH net-next 04/12] rocker: Handle SWITCHDEV_PORT_OBJ_ADD/_DEL Petr Machata
2018-11-22 23:29 ` [PATCH net-next 05/12] net: dsa: slave: " Petr Machata
2018-11-22 23:29 ` [PATCH net-next 06/12] staging: fsl-dpaa2: ethsw: Introduce ethsw_port_dev_check() Petr Machata
2018-11-22 23:29 ` [PATCH net-next 07/12] staging: fsl-dpaa2: ethsw: Handle SWITCHDEV_PORT_OBJ_ADD/_DEL Petr Machata
2018-11-22 23:29 ` [PATCH net-next 08/12] switchdev: Add helpers to aid traversal through lower devices Petr Machata
2018-11-22 23:29 ` [PATCH net-next 09/12] mlxsw: spectrum_switchdev: Handle SWITCHDEV_PORT_OBJ_ADD/_DEL Petr Machata
2018-11-22 23:30 ` [PATCH net-next 10/12] ocelot: " Petr Machata
2018-11-22 23:32 ` [PATCH net-next 11/12] switchdev: Replace port obj add/del SDO with a notification Petr Machata
2018-11-22 23:48 ` [PATCH net-next 12/12] rocker, dsa, ethsw: Don't filter VLAN events on bridge itself Petr Machata
2018-11-23 1:40 ` [PATCH net-next 00/12] switchdev: Convert switchdev_port_obj_{add,del}() to notifiers Petr Machata
2018-11-24 2:02 ` 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=20181123.180244.2269656658446733343.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=devel@driverdev.osuosl.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=idosch@mellanox.com \
--cc=ioana.ciornei@nxp.com \
--cc=ivecera@redhat.com \
--cc=jiri@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=petrm@mellanox.com \
--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).