[lkml]   [2020]   [Jan]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC net-next v3 00/10] net: bridge: mrp: Add support for Media Redundancy Protocol (MRP)
On 24.01.2020 17:18, Horatiu Vultur wrote:
>Media Redundancy Protocol is a data network protocol standardized by
>International Electrotechnical Commission as IEC 62439-2. It allows rings of
>Ethernet switches to overcome any single failure with recovery time faster than
>STP. It is primarily used in Industrial Ethernet applications.
>Based on the previous RFC[1][2], the MRP state machine and all the
>timers were moved to userspace. A generic netlink interface is added to
>allow configuring the HW, and logic added to to implement the MRP
>specific forwarding rules.
>The userspace application that is using the new netlink can be found here[3].
>The current implementation both in kernel and userspace supports only 2 roles:
> MRM - this one is responsible to send MRP_Test and MRP_Topo frames on both
> ring ports. It needs to process MRP_Test to know if the ring is open or
> closed. This operation is desired to be offloaded to the HW because it
> requires to generate and process up to 4000 frames per second. Whenever it
> detects that the ring open it sends MRP_Topo frames to notify all MRC about
> changes in the topology. MRM needs also to process MRP_LinkChange frames,
> these frames are generated by the MRC. When the ring is open the the state
> of both ports is to forward frames and when the ring is closed then the
> secondary port is blocked.
> MRC - this one is responsible to forward MRP frames between the ring ports.
> In case one of the ring ports gets a link down or up, then MRC will generate
> a MRP_LinkChange frames. This node should also process MRP_Topo frames and to
> clear its FDB when it receives this frame.
> Userspace
> Deamon +----------+ Client
> +
> |
> +--------------|-----------------------------------------+
> Kernel |
> + Netlink
> | + Interrupt
> | |
> +--------------|------------------------------|----------+
> HW | Switchdev |
> + |
>The user interacts using the client (called 'mrp'), the client talks to the
>deamon (called 'mrp_server'), which talks with the kernel using netlink. The
>kernel will try to offload the requests to the HW via switchdev API. For this a
>new generic netlink interface was added to the bridge.
>If the kernel cannot offload MRP to HW (maybe it does not have a switchdev
>driver, or it is just not supported), then all the netlink calls will return
>-EOPNOTSUPP. In this case the user-space deamon fallback to SW only
Horatiu and I have spend a bit of time discussing what you be best here.
An alternative to this would be to do the SW fallback in the kernel,
instead of user-land. This would mean that the user application does not
need to know if the function is offloaded (or partly offloaded) to HW.

We went with this approch to make the kernel part as simple as possible.
The alternative would still be much simpler than the first version
posted - but it would require a bit more.

Both options has pros and cons, and we looking forward to the
community's view on this.

>There are required changes to the SW bridge to be able to run the MRP. First the
>bridge needs to initialize the netlink interface. And second it needs to know if
>a MRP frame was received on a MRP ring port. In case it was received the SW
>bridge should not forward the frame it needs to redirected to upper layes. In
>case it was not received on a ring port then it just forwards it as usual.
>To be able to offload this to the HW, it was required to extend the switchdev
>If this will be accepted then in the future the netlink interface can be
>expended with multiple attributes which are required by different roles of the
>MRP. Like Media Redundancy Automanager(MRA), Media Interconnect Manager(MIM) and
>Media Interconnect Client(MIC).
>Horatiu Vultur (10):
> net: bridge: mrp: Expose mrp attributes.
> net: bridge: mrp: Expose function br_mrp_port_open
> net: bridge: mrp: Add MRP interface used by netlink
> net: bridge: mrp: Add generic netlink interface to configure MRP
> net: bridge: mrp: Update MRP interface to add switchdev support
> net: bridge: mrp: switchdev: Extend switchdev API to offload MRP
> net: bridge: mrp: switchdev: Implement MRP API for switchdev
> net: bridge: mrp: Connect MRP api with the switchev API
> net: bridge: mrp: Integrate MRP into the bridge
> net: bridge: mrp: Update Kconfig and Makefile
> include/linux/mrp_bridge.h | 25 ++
> include/net/switchdev.h | 51 +++
> include/uapi/linux/if_ether.h | 1 +
> include/uapi/linux/mrp_bridge.h | 118 ++++++
> net/bridge/Kconfig | 12 +
> net/bridge/Makefile | 2 +
> net/bridge/br.c | 11 +
> net/bridge/br_device.c | 3 +
> net/bridge/br_if.c | 6 +
> net/bridge/br_input.c | 14 +
> net/bridge/br_mrp.c | 193 ++++++++++
> net/bridge/br_mrp_netlink.c | 655 ++++++++++++++++++++++++++++++++
> net/bridge/br_mrp_switchdev.c | 147 +++++++
> net/bridge/br_private.h | 14 +
> net/bridge/br_private_mrp.h | 58 +++
> 15 files changed, 1310 insertions(+)
> create mode 100644 include/linux/mrp_bridge.h
> create mode 100644 include/uapi/linux/mrp_bridge.h
> create mode 100644 net/bridge/br_mrp.c
> create mode 100644 net/bridge/br_mrp_netlink.c
> create mode 100644 net/bridge/br_mrp_switchdev.c
> create mode 100644 net/bridge/br_private_mrp.h

 \ /
  Last update: 2020-01-24 21:34    [W:0.372 / U:1.284 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site