lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 3 Aug 2021 08:02:26 -0400
From:   Jamal Hadi Salim <>
To:     Vlad Buslov <>
Cc:     Simon Horman <>,
        David Miller <>,
        Jakub Kicinski <>,
        Cong Wang <>,
        Jiri Pirko <>,,, Baowen Zheng <>,
        Louis Peens <>,
        Ido Schimmel <>,
        Jiri Pirko <>, Roopa Prabhu <>
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 <> 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:


Powered by blists - more mailing lists