[PATCH v3 08/19] net/ixgbe: reimplement ntuple parser

[Burakov, Anatoly]

On 9/19/2026 6:11 PM, Medvedkin, Vladimir wrote:
> 
> On 9/16/2026 1:18 PM, Anatoly Burakov wrote:
>> Use the new flow graph API and the common parsing framework to implement
>> flow parser for ntuple.
>>
>> The 5tuple filter tracking infrastructure is moved completely inside the
>> new engine and is removed from the rest of the driver.
>>
>> Signed-off-by: Anatoly Burakov<anatoly.burakov at intel.com>
>> ---

<snip>

>> +    priority = RTE_MIN(IXGBE_MAX_N_TUPLE_PRIO - 1, (uint16_t)attr- 
>> >priority);
>> +    priority = IXGBE_MAX_N_TUPLE_PRIO - 1 - priority;
>> +    priority += IXGBE_MIN_N_TUPLE_PRIO;
>> +    ntuple_ctx->ntuple.priority = priority;
> 
> priority = RTE_MIN(IXGBE_MAX_N_TUPLE_PRIO, 
> RTE_MAX(IXGBE_MIN_N_TUPLE_PRIO, attr->priority))
> 
> otherwise priority 0 maps to 7

According to data sheet and rte_flow API semantics, this should be 
correct. Priority 0 is highest in rte_flow, priority 7 is highest as far 
as ntuple filters are concerned. The old priority assignment was 
semantically incorrect. This probably should be a separate fix.

-- 
Thanks,
Anatoly