[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210129190114.3f5b6b44@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Fri, 29 Jan 2021 19:01:14 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: <rasmus.villemoes@...vas.dk>, <andrew@...n.ch>,
Vladimir Oltean <vladimir.oltean@....com>
Cc: Horatiu Vultur <horatiu.vultur@...rochip.com>, <jiri@...nulli.us>,
<ivecera@...hat.com>, <davem@...emloft.net>, <roopa@...dia.com>,
<nikolay@...dia.com>, <netdev@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <bridge@...ts.linux-foundation.org>
Subject: Re: [PATCH net-next v2 0/4] bridge: mrp: Extend br_mrp_switchdev_*
On Wed, 27 Jan 2021 21:52:37 +0100 Horatiu Vultur wrote:
> This patch series extends MRP switchdev to allow the SW to have a better
> understanding if the HW can implement the MRP functionality or it needs
> to help the HW to run it. There are 3 cases:
> - when HW can't implement at all the functionality.
> - when HW can implement a part of the functionality but needs the SW
> implement the rest. For example if it can't detect when it stops
> receiving MRP Test frames but it can copy the MRP frames to CPU to
> allow the SW to determine this. Another example is generating the MRP
> Test frames. If HW can't do that then the SW is used as backup.
> - when HW can implement completely the functionality.
>
> So, initially the SW tries to offload the entire functionality in HW, if
> that fails it tries offload parts of the functionality in HW and use the
> SW as helper and if also this fails then MRP can't run on this HW.
>
> v2:
> - fix typos in comments and in commit messages
> - remove some of the comments
> - move repeated code in helper function
> - fix issue when deleting a node when sw_backup was true
Folks who were involved in previous MRP conversations - does this look
good to you? Anyone planning to test?
Powered by blists - more mailing lists