tree 0008a1e92f56326039672b6b5f9c87d18ccaf444
parent 0ba3aa254ae9d48ec0b2ecfa5fda5c391862a36b
author Lukasz Czapnik <lukasz.czapnik@intel.com> 1779364200 +0200
committer Tony Nguyen <anthony.l.nguyen@intel.com> 1780078362 -0700

ice: use ACL for ntuple rules that conflict with FDir

Flow Director can keep only one input set per flow type. After ACL support
was added for ethtool ntuple rules, the driver still only selected ACL for
rules with partial masks.

That leaves a gap for rules with full masks that still require a different
input set than the one already programmed for Flow Director. Such rules go
through the FDir path, build a different extraction sequence and then fail
because the existing FDir profile cannot be reused.

Detect this case before programming the rule. Build the candidate IP flow
segment, compare it with the active non-tunneled FDir profile and, when the
input sets differ, offload the rule through ACL if ACL is available.

Refactor the IP flow segment setup into a helper so the same logic can be
used both by the extraction-sequence configuration path and by the conflict
check.

Signed-off-by: Lukasz Czapnik <lukasz.czapnik@intel.com>