[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20190618.222624.192769316432594413.davem@davemloft.net>
Date: Tue, 18 Jun 2019 22:26:24 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: maxime.chevallier@...tlin.com
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
antoine.tenart@...tlin.com, thomas.petazzoni@...tlin.com,
gregory.clement@...tlin.com, miquel.raynal@...tlin.com,
nadavh@...vell.com, stefanc@...vell.com, mw@...ihalf.com,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH net-next 0/4] net: mvpp2: cls: Allow steering based on
vlan tag
From: Maxime Chevallier <maxime.chevallier@...tlin.com>
Date: Tue, 18 Jun 2019 16:55:15 +0200
> The PPv2 classifier can perform flow steering based on keys extracted
> from the VLAN tag. This series adds support for using the vlan id and
> the vlan prio as keys, using the ethtool interface.
>
> Patch 1 is a preparatory patch that prevent false-positive matches,
> using a dedicated lookup id for the RSS C2 lookup.
>
> Patch 2 allows to separate the flows based on the header fields they
> contain. The main goal is to be able to separate tagged traffic from
> untagged traffic for flow steering, just as we already do for RSS.
>
> Patch 3 solves an issue we have when extracting fields that aren't full
> bytes, such as the vlan tag which is 12 bits wide, or the priority which
> is 3 bits wide.
>
> Finally, patch 4 adds support for steering based on both vlan id and
> priority, extracted from the outermost tag.
Series applied, thanks.
Powered by blists - more mailing lists