From: Horatiu Vultur <horatiu.vultur@microchip.com> To: <nikolay@cumulusnetworks.com>, <roopa@cumulusnetworks.com>, <davem@davemloft.net>, <kuba@kernel.org>, <jiri@resnulli.us>, <ivecera@redhat.com>, <andrew@lunn.ch>, <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 00/12] bridge: mrp: Add support for interconnect ring Date: Mon, 6 Jul 2020 11:18:30 +0200 [thread overview] Message-ID: <20200706091842.3324565-1-horatiu.vultur@microchip.com> (raw) This patch series extends existing MRP to add support for interconnect ring. An interconnect ring is a ring that connects 2 rings. In this way is possible to connect multiple rings. Each interconnect ring is form of 4 nodes, in which 3 have the role MIC(Media Redundancy Interconnect Client) and one has the role MIM(Media Redundancy Interconnect Manager). All these nodes need to have the same ID and the ID needs to be unique between multiple interconnect rings. And 2 nodes needs to be part of one ring and the other 2 nodes needs to be part of the other ring that is connected. +---------+ | | +----------| MRM |---------------+ | | | | | +---------+ | | | | | | | +--------------+ +-----------------+ | | | | | MRC/MIC |------------------| MRC/MIM | | | | | +--------------+ +-----------------+ | | |Interconnect port |Interconnect port | | | | +--------------+ +-----------------+ | | | | | MRC/MIC |----------------- | MRC/MIC | | | | | +--------------+ +-----------------+ | | | | | +---------+ | | | | | +----------| MRM |----------------+ | | +---------+ Each node in a ring needs to have one of the following ring roles, MRM or MRC. And it can also have an interconnect role like MIM or MIC if it is part of an interconnect ring. In the figure above the MRM doesn't have any interconnect role but the MRC from the top ring have the interconnect roles MIC respectively MIM. Therefore it is not possible for a node to have only an interconnect role. There are 2 ways for interconnect ring to detect when is open or closed: 1. To use CCM frames on the interconnect port to detect when the interconnect link goes down/up. This mode is called LC-mode. 2. To send InTest frames on all 3 ports(2 ring ports and 1 interconnect port) and detect when these frames are received back. This mode is called RC-mode. This patch series adds support only for RC-mode. Where MIM sends InTest frames on all 3 ports and detects when it receives back the InTest. When it receives the InTest it means that the ring is closed so it would set the interconnect port in blocking state. If it stops receiving the InTest frames then it would set the port in forwarding state and it would send InTopo frames. These InTopo frames will be received by MRM nodes and process them. And then the MRM will send Topo frames in the rings so each client will clear its FDB. Horatiu Vultur (12): switchdev: mrp: Extend switchdev API for MRP Interconnect bridge: uapi: mrp: Extend MRP attributes for MRP interconnect bridge: mrp: Extend bridge interface bridge: mrp: Extend br_mrp for MRP interconnect bridge: mrp: Rename br_mrp_port_open to br_mrp_ring_port_open bridge: mrp: Add br_mrp_in_port_open function bridge: switchdev: mrp: Extend MRP API for switchdev for MRP Interconnect bridge: mrp: Implement the MRP Interconnect API bridge: mrp: Extend MRP netlink interface for configuring MRP interconnect bridge: uapi: mrp: Extend MRP_INFO attributes for interconnect status bridge: mrp: Extend br_mrp_fill_info net: bridge: Add port attribute IFLA_BRPORT_MRP_IN_OPEN include/linux/if_bridge.h | 1 + include/net/switchdev.h | 38 +++ include/uapi/linux/if_bridge.h | 58 ++++ include/uapi/linux/if_link.h | 1 + include/uapi/linux/mrp_bridge.h | 38 +++ net/bridge/br_mrp.c | 531 +++++++++++++++++++++++++++-- net/bridge/br_mrp_netlink.c | 182 +++++++++- net/bridge/br_mrp_switchdev.c | 62 ++++ net/bridge/br_netlink.c | 3 + net/bridge/br_private_mrp.h | 27 +- tools/include/uapi/linux/if_link.h | 1 + 11 files changed, 906 insertions(+), 36 deletions(-) -- 2.27.0
WARNING: multiple messages have this Message-ID (diff)
From: Horatiu Vultur <horatiu.vultur@microchip.com> To: nikolay@cumulusnetworks.com, roopa@cumulusnetworks.com, davem@davemloft.net, kuba@kernel.org, jiri@resnulli.us, ivecera@redhat.com, andrew@lunn.ch, 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: [Bridge] [PATCH net-next 00/12] bridge: mrp: Add support for interconnect ring Date: Mon, 6 Jul 2020 11:18:30 +0200 [thread overview] Message-ID: <20200706091842.3324565-1-horatiu.vultur@microchip.com> (raw) This patch series extends existing MRP to add support for interconnect ring. An interconnect ring is a ring that connects 2 rings. In this way is possible to connect multiple rings. Each interconnect ring is form of 4 nodes, in which 3 have the role MIC(Media Redundancy Interconnect Client) and one has the role MIM(Media Redundancy Interconnect Manager). All these nodes need to have the same ID and the ID needs to be unique between multiple interconnect rings. And 2 nodes needs to be part of one ring and the other 2 nodes needs to be part of the other ring that is connected. +---------+ | | +----------| MRM |---------------+ | | | | | +---------+ | | | | | | | +--------------+ +-----------------+ | | | | | MRC/MIC |------------------| MRC/MIM | | | | | +--------------+ +-----------------+ | | |Interconnect port |Interconnect port | | | | +--------------+ +-----------------+ | | | | | MRC/MIC |----------------- | MRC/MIC | | | | | +--------------+ +-----------------+ | | | | | +---------+ | | | | | +----------| MRM |----------------+ | | +---------+ Each node in a ring needs to have one of the following ring roles, MRM or MRC. And it can also have an interconnect role like MIM or MIC if it is part of an interconnect ring. In the figure above the MRM doesn't have any interconnect role but the MRC from the top ring have the interconnect roles MIC respectively MIM. Therefore it is not possible for a node to have only an interconnect role. There are 2 ways for interconnect ring to detect when is open or closed: 1. To use CCM frames on the interconnect port to detect when the interconnect link goes down/up. This mode is called LC-mode. 2. To send InTest frames on all 3 ports(2 ring ports and 1 interconnect port) and detect when these frames are received back. This mode is called RC-mode. This patch series adds support only for RC-mode. Where MIM sends InTest frames on all 3 ports and detects when it receives back the InTest. When it receives the InTest it means that the ring is closed so it would set the interconnect port in blocking state. If it stops receiving the InTest frames then it would set the port in forwarding state and it would send InTopo frames. These InTopo frames will be received by MRM nodes and process them. And then the MRM will send Topo frames in the rings so each client will clear its FDB. Horatiu Vultur (12): switchdev: mrp: Extend switchdev API for MRP Interconnect bridge: uapi: mrp: Extend MRP attributes for MRP interconnect bridge: mrp: Extend bridge interface bridge: mrp: Extend br_mrp for MRP interconnect bridge: mrp: Rename br_mrp_port_open to br_mrp_ring_port_open bridge: mrp: Add br_mrp_in_port_open function bridge: switchdev: mrp: Extend MRP API for switchdev for MRP Interconnect bridge: mrp: Implement the MRP Interconnect API bridge: mrp: Extend MRP netlink interface for configuring MRP interconnect bridge: uapi: mrp: Extend MRP_INFO attributes for interconnect status bridge: mrp: Extend br_mrp_fill_info net: bridge: Add port attribute IFLA_BRPORT_MRP_IN_OPEN include/linux/if_bridge.h | 1 + include/net/switchdev.h | 38 +++ include/uapi/linux/if_bridge.h | 58 ++++ include/uapi/linux/if_link.h | 1 + include/uapi/linux/mrp_bridge.h | 38 +++ net/bridge/br_mrp.c | 531 +++++++++++++++++++++++++++-- net/bridge/br_mrp_netlink.c | 182 +++++++++- net/bridge/br_mrp_switchdev.c | 62 ++++ net/bridge/br_netlink.c | 3 + net/bridge/br_private_mrp.h | 27 +- tools/include/uapi/linux/if_link.h | 1 + 11 files changed, 906 insertions(+), 36 deletions(-) -- 2.27.0
next reply other threads:[~2020-07-06 9:20 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-06 9:18 Horatiu Vultur [this message] 2020-07-06 9:18 ` [Bridge] [PATCH net-next 00/12] bridge: mrp: Add support for interconnect ring Horatiu Vultur 2020-07-06 9:18 ` [PATCH net-next 01/12] switchdev: mrp: Extend switchdev API for MRP Interconnect Horatiu Vultur 2020-07-06 9:18 ` [Bridge] " Horatiu Vultur 2020-07-06 19:26 ` David Miller 2020-07-06 19:26 ` [Bridge] " David Miller 2020-07-07 10:38 ` Horatiu Vultur 2020-07-07 10:38 ` [Bridge] " Horatiu Vultur 2020-07-06 9:18 ` [PATCH net-next 02/12] bridge: uapi: mrp: Extend MRP attributes for MRP interconnect Horatiu Vultur 2020-07-06 9:18 ` [Bridge] " Horatiu Vultur 2020-07-06 19:27 ` David Miller 2020-07-06 19:27 ` [Bridge] " David Miller 2020-07-07 10:39 ` Horatiu Vultur 2020-07-07 10:39 ` [Bridge] " Horatiu Vultur 2020-07-06 9:18 ` [PATCH net-next 03/12] bridge: mrp: Extend bridge interface Horatiu Vultur 2020-07-06 9:18 ` [Bridge] " Horatiu Vultur 2020-07-06 9:18 ` [PATCH net-next 04/12] bridge: mrp: Extend br_mrp for MRP interconnect Horatiu Vultur 2020-07-06 9:18 ` [Bridge] " Horatiu Vultur 2020-07-06 9:18 ` [PATCH net-next 05/12] bridge: mrp: Rename br_mrp_port_open to br_mrp_ring_port_open Horatiu Vultur 2020-07-06 9:18 ` [Bridge] " Horatiu Vultur 2020-07-06 9:18 ` [PATCH net-next 06/12] bridge: mrp: Add br_mrp_in_port_open function Horatiu Vultur 2020-07-06 9:18 ` [Bridge] " Horatiu Vultur 2020-07-06 9:18 ` [PATCH net-next 07/12] bridge: switchdev: mrp: Extend MRP API for switchdev for MRP Interconnect Horatiu Vultur 2020-07-06 9:18 ` [Bridge] " Horatiu Vultur 2020-07-06 9:18 ` [PATCH net-next 08/12] bridge: mrp: Implement the MRP Interconnect API Horatiu Vultur 2020-07-06 9:18 ` [Bridge] " Horatiu Vultur 2020-07-07 13:27 ` Nikolay Aleksandrov 2020-07-07 13:27 ` [Bridge] " Nikolay Aleksandrov 2020-07-07 14:11 ` Horatiu Vultur 2020-07-07 14:11 ` [Bridge] " Horatiu Vultur 2020-07-06 9:18 ` [PATCH net-next 09/12] bridge: mrp: Extend MRP netlink interface for configuring MRP interconnect Horatiu Vultur 2020-07-06 9:18 ` [Bridge] " Horatiu Vultur 2020-07-06 9:18 ` [PATCH net-next 10/12] bridge: uapi: mrp: Extend MRP_INFO attributes for interconnect status Horatiu Vultur 2020-07-06 9:18 ` [Bridge] " Horatiu Vultur 2020-07-06 9:18 ` [PATCH net-next 11/12] bridge: mrp: Extend br_mrp_fill_info Horatiu Vultur 2020-07-06 9:18 ` [Bridge] " Horatiu Vultur 2020-07-06 9:18 ` [PATCH net-next 12/12] net: bridge: Add port attribute IFLA_BRPORT_MRP_IN_OPEN Horatiu Vultur 2020-07-06 9:18 ` [Bridge] " Horatiu Vultur
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=20200706091842.3324565-1-horatiu.vultur@microchip.com \ --to=horatiu.vultur@microchip.com \ --cc=UNGLinuxDriver@microchip.com \ --cc=andrew@lunn.ch \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.