From: David Miller <davem@davemloft.net>
To: horatiu.vultur@microchip.com
Cc: nikolay@cumulusnetworks.com, jiri@resnulli.us,
ivecera@redhat.com, kuba@kernel.org, roopa@cumulusnetworks.com,
olteanv@gmail.com, andrew@lunn.ch, UNGLinuxDriver@microchip.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
bridge@lists.linux-foundation.org
Subject: Re: [PATCH net-next v4 00/11] net: bridge: mrp: Add support for Media Redundancy Protocol(MRP)
Date: Mon, 27 Apr 2020 11:40:50 -0700 (PDT) [thread overview]
Message-ID: <20200427.114050.2017715904275832358.davem@davemloft.net> (raw)
In-Reply-To: <20200426132208.3232-1-horatiu.vultur@microchip.com>
From: Horatiu Vultur <horatiu.vultur@microchip.com>
Date: Sun, 26 Apr 2020 15:21:57 +0200
> 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][3][4][5], and patches[6][7][8], the MRP state
> machine and all the timers were moved to userspace, except for the timers used
> to generate MRP Test frames. In this way the userspace doesn't know and should
> not know if the HW or the kernel will generate the MRP Test frames. The
> following changes were added to the bridge to support the MRP:
> - the existing netlink interface was extended with MRP support,
> - allow to detect when a MRP frame was received on a MRP ring port
> - allow MRP instance to forward/terminate MRP frames
> - generate MRP Test frames in case the HW doesn't have support for this
>
> To be able to offload MRP support to HW, the switchdev API was extend.
...
Series applied, thank you.
prev parent reply other threads:[~2020-04-27 18:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 13:21 [PATCH net-next v4 00/11] net: bridge: mrp: Add support for Media Redundancy Protocol(MRP) Horatiu Vultur
2020-04-26 13:21 ` [PATCH net-next v4 01/11] bridge: uapi: mrp: Add mrp attributes Horatiu Vultur
2020-04-26 13:21 ` [PATCH net-next v4 02/11] bridge: mrp: Update Kconfig Horatiu Vultur
2020-04-27 9:46 ` Sergei Shtylyov
2020-04-26 13:22 ` [PATCH net-next v4 03/11] bridge: mrp: Extend bridge interface Horatiu Vultur
2020-04-26 13:22 ` [PATCH net-next v4 04/11] net: bridge: Add port attribute IFLA_BRPORT_MRP_RING_OPEN Horatiu Vultur
2020-04-26 13:22 ` [PATCH net-next v4 05/11] bridge: mrp: Add MRP interface Horatiu Vultur
2020-04-26 13:22 ` [PATCH net-next v4 06/11] switchdev: mrp: Extend switchdev API to offload MRP Horatiu Vultur
2020-04-26 13:22 ` [PATCH net-next v4 07/11] bridge: switchdev: mrp: Implement MRP API for switchdev Horatiu Vultur
2020-04-26 13:22 ` [PATCH net-next v4 08/11] bridge: mrp: Connect MRP API with the switchdev API Horatiu Vultur
2020-04-26 13:22 ` [PATCH net-next v4 09/11] bridge: mrp: Implement netlink interface to configure MRP Horatiu Vultur
2020-04-26 13:22 ` [PATCH net-next v4 10/11] bridge: mrp: Integrate MRP into the bridge Horatiu Vultur
2020-04-26 13:22 ` [PATCH net-next v4 11/11] net: bridge: Add checks for enabling the STP Horatiu Vultur
2020-04-27 18:40 ` 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=20200427.114050.2017715904275832358.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=bridge@lists.linux-foundation.org \
--cc=horatiu.vultur@microchip.com \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=olteanv@gmail.com \
--cc=roopa@cumulusnetworks.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).