[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200225130223.kb7jg7u2kgjjrlpo@lx-anielsen.microsemi.net>
Date: Tue, 25 Feb 2020 14:02:23 +0100
From: "Allan W. Nielsen" <allan.nielsen@...rochip.com>
To: Vladimir Oltean <olteanv@...il.com>
CC: <davem@...emloft.net>, <horatiu.vultur@...rochip.com>,
<alexandre.belloni@...tlin.com>, <andrew@...n.ch>,
<f.fainelli@...il.com>, <vivien.didelot@...il.com>,
<joergen.andreasen@...rochip.com>, <alexandru.marginean@....com>,
<claudiu.manoil@....com>, <xiaoliang.yang_1@....com>,
<yangbo.lu@....com>, <netdev@...r.kernel.org>,
<UNGLinuxDriver@...rochip.com>
Subject: Re: [PATCH v2 net-next 0/2] Allow unknown unicast traffic to CPU for
Felix DSA
On 24.02.2020 23:34, Vladimir Oltean wrote:
>From: Vladimir Oltean <vladimir.oltean@....com>
>
>This is the continuation of the previous "[PATCH net-next] net: mscc:
>ocelot: Workaround to allow traffic to CPU in standalone mode":
>
>https://www.spinics.net/lists/netdev/msg631067.html
>
>Following the feedback received from Allan Nielsen, the Ocelot and Felix
>drivers were made to use the CPU port module in the same way (patch 1),
>and Felix was made to additionally allow unknown unicast frames towards
>the CPU port module (patch 2).
>
>Vladimir Oltean (2):
> net: mscc: ocelot: eliminate confusion between CPU and NPI port
> net: dsa: felix: Allow unknown unicast traffic towards the CPU port
> module
>
> drivers/net/dsa/ocelot/felix.c | 16 ++++--
> drivers/net/ethernet/mscc/ocelot.c | 62 +++++++++++++---------
> drivers/net/ethernet/mscc/ocelot.h | 10 ----
> drivers/net/ethernet/mscc/ocelot_board.c | 5 +-
> include/soc/mscc/ocelot.h | 67 ++++++++++++++++++++++--
> net/dsa/tag_ocelot.c | 3 +-
> 6 files changed, 117 insertions(+), 46 deletions(-)
Hi Vladimer,
Did this fix you original issue with the spamming of the CPU?
/Allan
Powered by blists - more mailing lists