Searched refs:fate (Results 1 – 3 of 3) sorted by relevance
155 ingress or egress traffic, alter its fate and query related counters according
12 traffic, alter its fate and query related counters according to any1664 - Actions that modify the fate of matching traffic, for instance by dropping1674 fate kind results in undefined behavior. This applies to both ingress and3003 applied with own set of actions with a fate action, the packets sampled3008 packets, and must have a fate action.
5215 uint8_t fate = final_policy->act_cnt[i].fate_action; in get_meter_sub_policy() local5217 if (fate == MLX5_FLOW_FATE_SHARED_RSS) { in get_meter_sub_policy()5258 } else if (fate == MLX5_FLOW_FATE_QUEUE) { in get_meter_sub_policy()