> -----Original Message-----
> From: Intel-wired-lan <[email protected]> On Behalf Of 
> Marcin Szycik
> Sent: 02 July 2026 16:00
> To: [email protected]
> Cc: [email protected]; Penigalapati, Sandeep 
> <[email protected]>; S, Ananth <[email protected]>; 
> [email protected]; Nguyen, Anthony L <[email protected]>; 
> Marcin Szycik <[email protected]>
> Subject: [Intel-wired-lan] [PATCH iwl-next v5 10/12] ice: add ACL reset 
> recovery and NTUPLE feature toggle
>
> Extend ACL support to survive PF resets. Add ice_acl_replay_flows() to 
> rebuild HW flow profiles from preserved SW state, and
> ice_acl_replay_fltrs() to reprogram TCAM entries from the SW filter list. 
> Wire both into ice_rebuild(). On failure, don't fail reset, rather delete all 
> ACL filters from the SW list.
>
> Reset per-profile HW extraction sequences and range checkers for all profiles 
> inside ice_acl_create_hw(). This state is separate from the TCAM entries and 
> survives a PF reset. Explicitly clearing it ensures that the old 
> configuration is erased.
>
> Add the ICE_FLAG_ACL_ENA PF flag to track ACL status. ACL is always 
> available, so set it unconditionally in driver initialization. Use the new 
> flag to track the NTUPLE ethtool feature flag, alongside Flow Director, as 
> both blocks are used to implement ethtool NTUPLE filters.
> Like with Flow Director, disabling the flag deletes all filters, but enabling 
> it does not reprogram filters.
>
> Signed-off-by: Marcin Szycik <[email protected]>
> ---
> v5:
> * Add this patch
> ---
> drivers/net/ethernet/intel/ice/ice.h          |  4 +
> drivers/net/ethernet/intel/ice/ice_acl.h      |  5 +-
> drivers/net/ethernet/intel/ice/ice_acl_main.h |  1 +  
> drivers/net/ethernet/intel/ice/ice_acl_ctrl.c | 43 +++++-----  
> drivers/net/ethernet/intel/ice/ice_acl_main.c | 47 +++++++++++
> .../ethernet/intel/ice/ice_ethtool_ntuple.c   | 79 +++++++++++++++++++
> drivers/net/ethernet/intel/ice/ice_main.c     | 47 +++++++++++
> 7 files changed, 201 insertions(+), 25 deletions(-)
>

Tested-by: Rinitha S <[email protected]> (A Contingent worker at Intel)

Reply via email to