[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <996ecc2d-d982-c7f3-7769-3b489d5ff66c@mojatatu.com>
Date: Tue, 3 Aug 2021 08:02:26 -0400
From: Jamal Hadi Salim <jhs@...atatu.com>
To: Vlad Buslov <vladbu@...dia.com>
Cc: Simon Horman <simon.horman@...igine.com>,
David Miller <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Cong Wang <xiyou.wangcong@...il.com>,
Jiri Pirko <jiri@...lanox.com>, netdev@...r.kernel.org,
oss-drivers@...igine.com, Baowen Zheng <baowen.zheng@...igine.com>,
Louis Peens <louis.peens@...igine.com>,
Ido Schimmel <idosch@...dia.com>,
Jiri Pirko <jiri@...nulli.us>, Roopa Prabhu <roopa@...dia.com>
Subject: tc offload debug-ability
I just changed the subject line..
On 2021-08-03 5:57 a.m., Jamal Hadi Salim wrote:
> On 2021-07-30 7:40 a.m., Vlad Buslov wrote:
>> On Fri 30 Jul 2021 at 13:17, Jamal Hadi Salim <jhs@...atatu.com> wrote:
>>> On 2021-07-28 10:46 a.m., Simon Horman wrote:
>
>>
>> Filters with tunnel_key encap actions can be offloaded/unoffloaded
>> dynamically based on neigh state (see mlx5e_rep_neigh_update()) and fib
>> events (see mlx5e_tc_fib_event_work()).
>>
>
> Thanks. Will look and compare against the FIB case.
>
So unless i am mistaken Vlad:
a) there is no way to reflect the details when someone dumps the rules.
b) No notifications sent to the control plane (user space) when the
neighbor updates are offloaded.
My comments earlier are inspired by debugging tc offload and by this:
https://patches.linaro.org/cover/378345/
cheers,
jamal
Powered by blists - more mailing lists