[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20200601.115628.932125543367472654.davem@davemloft.net>
Date: Mon, 01 Jun 2020 11:56:28 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: horatiu.vultur@...rochip.com
Cc: nikolay@...ulusnetworks.com, roopa@...ulusnetworks.com,
jiri@...nulli.us, ivecera@...hat.com, kuba@...nel.org,
UNGLinuxDriver@...rochip.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, bridge@...ts.linux-foundation.org
Subject: Re: [PATCH net-next v2 0/3] bridge: mrp: Add support for MRA role
From: Horatiu Vultur <horatiu.vultur@...rochip.com>
Date: Sat, 30 May 2020 18:09:45 +0000
> 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.
>
> v2:
> - add new patch that fixes sparse warnings
> - fix parsing of prio attribute
Series applied, thank you.
Powered by blists - more mailing lists