From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: <nikolay@cumulusnetworks.com>, <roopa@cumulusnetworks.com>,
<jiri@resnulli.us>, <ivecera@redhat.com>, <davem@davemloft.net>,
<kuba@kernel.org>, <UNGLinuxDriver@microchip.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<bridge@lists.linux-foundation.org>
Cc: Horatiu Vultur <horatiu.vultur@microchip.com>
Subject: [PATCH net-next 0/2] bridge: mrp: Add support for MRA role
Date: Fri, 29 May 2020 10:05:12 +0000 [thread overview]
Message-ID: <20200529100514.920537-1-horatiu.vultur@microchip.com> (raw)
This patch series extends the MRP with the MRA role.
A node that has the MRA role can behave as a MRM or as a MRC. In case there are
multiple nodes in the topology that has the MRA role then only one node can
behave as MRM and all the others need to be have as MRC. The node that has the
higher priority(lower value) will behave as MRM.
A node that has the MRA role and behaves as MRC, it just needs to forward the
MRP_Test frames between the ring ports but also it needs to detect in case it
stops receiving MRP_Test frames. In that case it would try to behave as MRM.
Horatiu Vultur (2):
bridge: mrp: Set the priority of MRP instance
bridge: mrp: Add support for role MRA
include/net/switchdev.h | 2 +
include/uapi/linux/if_bridge.h | 4 +
include/uapi/linux/mrp_bridge.h | 38 ++++++++++
net/bridge/br_mrp.c | 128 +++++++++++++++++++++++++++-----
net/bridge/br_mrp_netlink.c | 11 +++
net/bridge/br_mrp_switchdev.c | 5 +-
net/bridge/br_private_mrp.h | 5 +-
7 files changed, 171 insertions(+), 22 deletions(-)
--
2.26.2
next reply other threads:[~2020-05-29 8:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 10:05 Horatiu Vultur [this message]
2020-05-29 10:05 ` [PATCH net-next 1/2] bridge: mrp: Set the priority of MRP instance Horatiu Vultur
2020-05-29 8:12 ` Nikolay Aleksandrov
2020-05-29 13:47 ` Horatiu Vultur
2020-05-29 10:05 ` [PATCH net-next 2/2] bridge: mrp: Add support for role MRA Horatiu Vultur
2020-05-29 19:18 ` Jakub Kicinski
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=20200529100514.920537-1-horatiu.vultur@microchip.com \
--to=horatiu.vultur@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--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=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).