Friday, October 12, 2018 11:43 AM, Yongseok Koh:
> Subject: [PATCH v4] net/mlx5: support multiple groups and jump action
>
> rte_flow has 'group' attribute and 'jump' action in order to support multiple
> groups. This feature is known as multi-table support ('chain' in linux TC
> flower) in general because a group means a table of flows. Example
> commands are:
>
> flow create 0 transfer priority 1 ingress
> pattern eth / vlan vid is 100 / end
> actions jump group 1 / end
>
> flow create 0 transfer priority 1 ingress
> pattern eth / vlan vid is 200 / end
> actions jump group 2 / end
>
> flow create 0 transfer group 1 priority 2 ingress
> pattern eth / vlan vid is 100 /
> ipv4 dst spec 192.168.40.0 dst prefix 24 / end
> actions drop / end
>
> flow create 0 transfer group 1 priority 2 ingress
> pattern end
> actions of_pop_vlan / port_id id 1 / end
>
> flow create 0 transfer group 2 priority 2 ingress
> pattern eth / vlan vid is 200 /
> ipv4 dst spec 192.168.40.0 dst prefix 24 / end
> actions of_pop_vlan / port_id id 2 / end
>
> flow create 0 transfer group 2 priority 2 ingress
> pattern end
> actions port_id id 2 / end
>
> With theses flows, if a packet having vlan 200 and src_ip as 192.168.40.1,
> this
> packet will firstly hit the 1st flow. Then it will hit the 5th flow because
> of the
> 'jump' action. As a result, the packet will be forwarded to port 2 (VF
> representor) with vlan tag being stripped off. If the packet had vlan 100
> instead, it would be dropped by the 3rd flow.
>
> Signed-off-by: Yongseok Koh <ys...@mellanox.com>
> ---
Applied to next-net-mlx, thanks.
