In non-pipeline mode, priority is ignored, a flow rule can be created as a flow director rule or a switch rule depends on its pattern/action. Hence removing the priority field check from ice_fdir_parse which is causing valid flow creation to return failure.
Signed-off-by: Dhanya Pillai <dhanya.r.pil...@intel.com> --- drivers/net/intel/ice/ice_fdir_filter.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/drivers/net/intel/ice/ice_fdir_filter.c b/drivers/net/intel/ice/ice_fdir_filter.c index 2ff0090aca..b11c8f170c 100644 --- a/drivers/net/intel/ice/ice_fdir_filter.c +++ b/drivers/net/intel/ice/ice_fdir_filter.c @@ -2446,7 +2446,7 @@ ice_fdir_parse(struct ice_adapter *ad, uint32_t array_len, const struct rte_flow_item pattern[], const struct rte_flow_action actions[], - uint32_t priority, + uint32_t priority __rte_unused, void **meta, struct rte_flow_error *error) { @@ -2461,8 +2461,6 @@ ice_fdir_parse(struct ice_adapter *ad, item = ice_search_pattern_match_item(ad, pattern, array, array_len, error); - if (priority >= 1) - return -rte_errno; if (!item) return -rte_errno; -- 2.43.0