[dpdk-dev] [PATCH v5 2/6] net/mlx5: support basic flow items and actions
Ferruh Yigit
ferruh.yigit at intel.com
Wed Jan 4 18:49:46 CET 2017
Hi Nelio,
A quick question.
On 12/29/2016 3:15 PM, Nelio Laranjeiro wrote:
> Introduce initial software for rte_flow rules.
>
> VLAN, VXLAN are still not supported.
>
> Signed-off-by: Nelio Laranjeiro <nelio.laranjeiro at 6wind.com>
> Acked-by: Adrien Mazarguil <adrien.mazarguil at 6wind.com>
<...>
> +static int
> +priv_flow_validate(struct priv *priv,
> + const struct rte_flow_attr *attr,
> + const struct rte_flow_item items[],
> + const struct rte_flow_action actions[],
> + struct rte_flow_error *error,
> + struct mlx5_flow *flow)
> +{
> + const struct mlx5_flow_items *cur_item = mlx5_flow_items;
<...>
> + for (; items->type != RTE_FLOW_ITEM_TYPE_END; ++items) {
<...>
> + }
> + for (; actions->type != RTE_FLOW_ACTION_TYPE_END; ++actions) {
<...>
> + }
Is it guarantied in somewhere that items or actions terminated with
TYPE_END?
And these fields are direct inputs from user.
Is there a way to verify user provided values are with TYPE_END terminated?
<...>
More information about the dev
mailing list