[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200419180143.ibexwjrlp3flla6z@ws.localdomain>
Date: Sun, 19 Apr 2020 20:01:43 +0200
From: "Allan W. Nielsen" <allan.nielsen@...rochip.com>
To: Ido Schimmel <idosch@...sch.org>
CC: Vladimir Oltean <olteanv@...il.com>, <davem@...emloft.net>,
<horatiu.vultur@...rochip.com>, <alexandre.belloni@...tlin.com>,
<antoine.tenart@...tlin.com>, <andrew@...n.ch>,
<f.fainelli@...il.com>, <vivien.didelot@...il.com>,
<joergen.andreasen@...rochip.com>, <claudiu.manoil@....com>,
<netdev@...r.kernel.org>, <UNGLinuxDriver@...rochip.com>,
<alexandru.marginean@....com>, <xiaoliang.yang_1@....com>,
<yangbo.lu@....com>, <po.liu@....com>, <jiri@...lanox.com>,
<kuba@...nel.org>
Subject: Re: [PATCH net-next] net: mscc: ocelot: deal with problematic
MAC_ETYPE VCAP IS2 rules
On 19.04.2020 11:30, Ido Schimmel wrote:
>Not sure I completely understand the difficulties you are facing, but it
>sounds similar to a problem we had in mlxsw. You might want to look into
>"chain templates" [1] in order to restrict the keys that can be used
>simultaneously.
Not sure I understood the details, but but sure it is the same issue we
are trying to solve.
>I don't mind participating in an online discussion if you think it can
>help.
I'm sure it would be helpfull to have someone with insight in the MLX
driver. I have been looking a lot at it, and there are large part of it
which I still have not understood.
If you get too borrowed you can always leave ;-)
/Allan
Powered by blists - more mailing lists