[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200110202455.vku455ioa7vaj4dn@soft-dev3.microsemi.net>
Date: Fri, 10 Jan 2020 21:24:55 +0100
From: Horatiu Vultur <horatiu.vultur@...rochip.com>
To: <nikolay@...ulusnetworks.com>
CC: David Miller <davem@...emloft.net>, <linux-kernel@...r.kernel.org>,
<netdev@...r.kernel.org>, <bridge@...ts.linux-foundation.org>,
<roopa@...ulusnetworks.com>, <jakub.kicinski@...ronome.com>,
<vivien.didelot@...il.com>, <andrew@...n.ch>,
<jeffrey.t.kirsher@...el.com>, <olteanv@...il.com>,
<anirudh.venkataramanan@...el.com>, <dsahern@...il.com>,
<jiri@...lanox.com>, <UNGLinuxDriver@...rochip.com>
Subject: Re: [RFC net-next Patch 0/3] net: bridge: mrp: Add support for Media
Redundancy Protocol(MRP)
> >With a userland implementation, what approach do you suggest for
> >DSA/switchdev offload
> >of this stuff?
>
> Good question, there was no mention of that initially, or I missed it at least.
> There aren't many details about what/how will be offloaded right now.
> We need more information about what will be offloaded and how it will fit.
I think we should do a new version of the RFC-Patch with the hooks to
offload included. Just the signatures and the invocations should give
the context we are missing in the discussion.
Depending on how the discussion goes from there, we can then either work
on putting this in user-space or fix the issues pointed out in the
original attempt.
/Horatiu
Powered by blists - more mailing lists