[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87wncqa77w.fsf@nvidia.com>
Date: Wed, 6 Jul 2022 12:57:48 +0300
From: Vlad Buslov <vladbu@...dia.com>
To: <davem@...emloft.net>, <kuba@...nel.org>, <saeedm@...dia.com>,
<vladimir.oltean@....com>, <claudiu.manoil@....com>,
<alexandre.belloni@...tlin.com>, <rajur@...lsio.com>,
<sgoutham@...vell.com>, <gakula@...vell.com>,
<sbhatta@...vell.com>, <hkelam@...vell.com>,
<simon.horman@...igine.com>
CC: <jianbol@...dia.com>, <idosch@...dia.com>,
<xiyou.wangcong@...il.com>, <jhs@...atatu.com>, <jiri@...nulli.us>,
<netdev@...r.kernel.org>, <maord@...dia.com>,
Vlad Buslov <vladbu@...dia.com>
Subject: Re: [PATCH net 0/2] Fix police 'continue' action offload
Adding maintainers of other drivers that might have been impacted by the
validation change. If your driver supports 'continue' police action
offload with matchall classifier, then you may want to also relax the
validation restrictions in similar manner as I do in patch 2 for mlx5,
as I also submitted OvS fix to restore matchall police notexceed action
type to 'continue' here:
https://mail.openvswitch.org/pipermail/ovs-dev/2022-July/395561.html
On Mon 04 Jul 2022 at 22:44, Vlad Buslov <vladbu@...dia.com> wrote:
> TC act_police with 'continue' action had been supported by mlx5 matchall
> classifier offload implementation for some time. However, 'continue' was
> assumed implicitly and recently got broken in multiple places. Fix it in
> both TC hardware offload validation code and mlx5 driver.
>
> Vlad Buslov (2):
> net/sched: act_police: allow 'continue' action offload
> net/mlx5e: Fix matchall police parameters validation
>
> drivers/net/ethernet/mellanox/mlx5/core/en_tc.c | 13 ++++++-------
> include/net/flow_offload.h | 1 +
> net/sched/act_police.c | 2 +-
> 3 files changed, 8 insertions(+), 8 deletions(-)
Powered by blists - more mailing lists