[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200715181340.5cf42a40@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Wed, 15 Jul 2020 18:13:40 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Ido Schimmel <idosch@...sch.org>
Cc: netdev@...r.kernel.org, davem@...emloft.net, jiri@...lanox.com,
petrm@...lanox.com, mlxsw@...lanox.com,
Ido Schimmel <idosch@...lanox.com>
Subject: Re: [PATCH net-next 00/11] mlxsw: Offload tc police action
On Wed, 15 Jul 2020 11:27:22 +0300 Ido Schimmel wrote:
> From: Ido Schimmel <idosch@...lanox.com>
>
> This patch set adds support for tc police action in mlxsw.
>
> Patches #1-#2 add defines for policer bandwidth limits and resource
> identifiers (e.g., maximum number of policers).
>
> Patch #3 adds a common policer core in mlxsw. Currently it is only used
> by the policy engine, but future patch sets will use it for trap
> policers and storm control policers. The common core allows us to share
> common logic between all policer types and abstract certain details from
> the various users in mlxsw.
>
> Patch #4 exposes the maximum number of supported policers and their
> current usage to user space via devlink-resource. This provides better
> visibility and also used for selftests purposes.
>
> Patches #5-#7 gradually add support for tc police action in the policy
> engine by calling into previously mentioned policer core.
>
> Patch #8 adds a generic selftest for tc-police that can be used with
> veth pairs or physical loopbacks.
>
> Patches #9-#11 add mlxsw-specific selftests.
Applied, thanks Ido!
Powered by blists - more mailing lists