[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YhUP0lVaq+M/mwdY@shredder>
Date: Tue, 22 Feb 2022 18:31:14 +0200
From: Ido Schimmel <idosch@...sch.org>
To: Baowen Zheng <baowen.zheng@...igine.com>
Cc: Vladimir Oltean <vladimir.oltean@....com>,
Jianbo Liu <jianbol@...dia.com>,
"olteanv@...il.com" <olteanv@...il.com>,
"andrew@...n.ch" <andrew@...n.ch>,
Claudiu Manoil <claudiu.manoil@....com>,
"vivien.didelot@...il.com" <vivien.didelot@...il.com>,
Petr Machata <petrm@...dia.com>,
"jhs@...atatu.com" <jhs@...atatu.com>,
oss-drivers <oss-drivers@...igine.com>,
"hkelam@...vell.com" <hkelam@...vell.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"leon@...nel.org" <leon@...nel.org>,
Nole Zhang <peng.zhang@...igine.com>,
"louis.peens@...ronome.com" <louis.peens@...ronome.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"alexandre.belloni@...tlin.com" <alexandre.belloni@...tlin.com>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"UNGLinuxDriver@...rochip.com" <UNGLinuxDriver@...rochip.com>,
"rajur@...lsio.com" <rajur@...lsio.com>,
Ido Schimmel <idosch@...dia.com>,
Simon Horman <simon.horman@...igine.com>,
"sbhatta@...vell.com" <sbhatta@...vell.com>,
"xiyou.wangcong@...il.com" <xiyou.wangcong@...il.com>,
Roi Dayan <roid@...dia.com>,
"kuba@...nel.org" <kuba@...nel.org>,
"jiri@...nulli.us" <jiri@...nulli.us>,
Saeed Mahameed <saeedm@...dia.com>,
"sgoutham@...vell.com" <sgoutham@...vell.com>,
"gakula@...vell.com" <gakula@...vell.com>,
"f.fainelli@...il.com" <f.fainelli@...il.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH net-next v2 2/2] flow_offload: reject offload for all
drivers with invalid police parameters
On Tue, Feb 22, 2022 at 10:29:57AM +0000, Baowen Zheng wrote:
> Since almost all the drivers that support to offload police action make the similar validation, if it make sense to add the validation in the file of flow_offload.h or flow_offload.c?
> Then the other drivers do not need to make the similar validation.
> WDYT?
But not all the drivers need the same validation. For example, nfp is
one of the few drivers that supports policing based on packet rate. The
octeontx2 driver has different restrictions based on whether the policer
is attached to matchall or flower.
We can put the restrictions that are common between all the drivers
somewhere, but it's not that much and it will also change over time,
resulting in needless churn where checks are moved to individual
drivers.
Powered by blists - more mailing lists