[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20200929.182658.204585143707913502.davem@davemloft.net>
Date: Tue, 29 Sep 2020 18:26:58 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: vladimir.oltean@....com
Cc: alexandre.belloni@...tlin.com, andrew@...n.ch,
f.fainelli@...il.com, vivien.didelot@...il.com,
horatiu.vultur@...rochip.com, joergen.andreasen@...rochip.com,
allan.nielsen@...rochip.com, alexandru.marginean@....com,
claudiu.manoil@....com, xiaoliang.yang_1@....com,
hongbo.wang@....com, netdev@...r.kernel.org, kuba@...nel.org,
UNGLinuxDriver@...rochip.com
Subject: Re: [PATCH net-next 00/13] HW support for VCAP IS1 and ES0 in
mscc_ocelot
From: Vladimir Oltean <vladimir.oltean@....com>
Date: Wed, 30 Sep 2020 01:27:20 +0300
> The patches from RFC series "Offload tc-flower to mscc_ocelot switch
> using VCAP chains" have been split into 2:
> https://patchwork.ozlabs.org/project/netdev/list/?series=204810&state=*
>
> This is the boring part, that deals with the prerequisites, and not with
> tc-flower integration. Apart from the initialization of some hardware
> blocks, which at this point still don't do anything, no new
> functionality is introduced.
>
> - Key and action field offsets are defined for the supported switches.
> - VCAP properties are added to the driver for the new TCAM blocks. But
> instead of adding them manually as was done for IS2, which is error
> prone, the driver is refactored to read these parameters from
> hardware, which is possible.
> - Some improvements regarding the processing of struct ocelot_vcap_filter.
> - Extending the code to be compatible with full and quarter keys.
>
> This series was tested, along with other patches not yet submitted, on
> the Felix and Seville switches.
Series applied, thanks.
Powered by blists - more mailing lists