4e05a229c5
In current implementation the calculation of the flow size is done during the validation stage, and the same function is also used to translate the input parameters into verbs spec. This is hard to maintain and error prone. Another issue is dev-flows (flows that are created implicitly in order to support the requested flow for example when the user request RSS on UDP 2 rules need to be created one for IPv4 and one for IPv6). In current implementation the dev-flows are created on the same memory allocation. This will be harder to implement in future drivers. The commits extract the calculation and creation of the dev-flow from the translation part (the part that converts the parameters into the format required by the driver). This results in that the prepare function only function is to allocate the dev-flow. Signed-off-by: Ori Kam <orika@mellanox.com> Acked-by: Yongseok Koh <yskoh@mellanox.com> |
||
---|---|---|
.. | ||
Makefile | ||
meson.build | ||
mlx5_defs.h | ||
mlx5_ethdev.c | ||
mlx5_flow.c | ||
mlx5_glue.c | ||
mlx5_glue.h | ||
mlx5_mac.c | ||
mlx5_mr.c | ||
mlx5_mr.h | ||
mlx5_nl_flow.c | ||
mlx5_nl.c | ||
mlx5_prm.h | ||
mlx5_rss.c | ||
mlx5_rxmode.c | ||
mlx5_rxq.c | ||
mlx5_rxtx_vec_neon.h | ||
mlx5_rxtx_vec_sse.h | ||
mlx5_rxtx_vec.c | ||
mlx5_rxtx_vec.h | ||
mlx5_rxtx.c | ||
mlx5_rxtx.h | ||
mlx5_socket.c | ||
mlx5_stats.c | ||
mlx5_trigger.c | ||
mlx5_txq.c | ||
mlx5_utils.h | ||
mlx5_vlan.c | ||
mlx5.c | ||
mlx5.h | ||
rte_pmd_mlx5_version.map |