From: Raslan Darawsheh <rasland@mellanox.com>
To: Jack Min <jackmin@mellanox.com>, Matan Azrad <matan@mellanox.com>,
Shahaf Shuler <shahafs@mellanox.com>,
Slava Ovsiienko <viacheslavo@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>,
Dekel Peled <dekelp@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/mlx5: fix push VLAN action wrongly use item info
Date: Wed, 15 Apr 2020 15:35:12 +0000 [thread overview]
Message-ID: <AM0PR05MB6707ACB34F7E56964AB78B38C2DB0@AM0PR05MB6707.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <e8e9d26be9ed806a43cb61b1519a3a2b8210fd62.1586747578.git.jackmin@mellanox.com>
Hi,
> -----Original Message-----
> From: Xiaoyu Min <jackmin@mellanox.com>
> Sent: Monday, April 13, 2020 6:29 AM
> To: Raslan Darawsheh <rasland@mellanox.com>; Matan Azrad
> <matan@mellanox.com>; Shahaf Shuler <shahafs@mellanox.com>; Slava
> Ovsiienko <viacheslavo@mellanox.com>
> Cc: dev@dpdk.org; stable@dpdk.org; Dekel Peled <dekelp@mellanox.com>
> Subject: [PATCH v2] net/mlx5: fix push VLAN action wrongly use item info
>
> Currently when PMD create push VLAN action it need to provide VID to HW
> and PMD get VID value from item VLAN in pattern if there is no
> of_set_vlan_vid action following.
>
> When user create rule like [1], which has of_set_vlan_vid action
> before of_push_vlan, the intention is to modify VID on existing VLAN
> header and push a new VLAN header with VID _inherit_ from the previous
> of_set_vlan_vid.
>
> Currently the above is not covered by PMD, PMD always fetch the VLAN
> information from item for of_push_vlan action.
>
> Fix it by only fetch VLAN information from item when there is no
> previous of_set_vlan_vid action.
>
> [1]: testpmd> flow create 2 ingress transfer group 1 priority 3 pattern
> eth / vlan vid is 2731 / ipv4 / end actions
> of_set_vlan_vid vlan_vid 3209 / of_push_vlan ethertype
> 0x88A8 / port_id id 1 / end
>
> Fixes: b8c0372bc5ac ("net/mlx5: fix set VLAN ID/PCP in new header")
> Cc: stable@dpdk.org
>
> Signed-off-by: Xiaoyu Min <jackmin@mellanox.com>
> Reviewed-by: Dekel Peled <dekelp@mellanox.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
> ---
> v2:
> - rebased
> - added Acked-by tag
>
> drivers/net/mlx5/mlx5_flow_dv.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/mlx5/mlx5_flow_dv.c
> b/drivers/net/mlx5/mlx5_flow_dv.c
> index 18ea577f8c..106d0b9461 100644
> --- a/drivers/net/mlx5/mlx5_flow_dv.c
> +++ b/drivers/net/mlx5/mlx5_flow_dv.c
> @@ -7511,7 +7511,9 @@ __flow_dv_translate(struct rte_eth_dev *dev,
> action_flags |=
> MLX5_FLOW_ACTION_OF_POP_VLAN;
> break;
> case RTE_FLOW_ACTION_TYPE_OF_PUSH_VLAN:
> - flow_dev_get_vlan_info_from_items(items, &vlan);
> + if (!(action_flags &
> + MLX5_FLOW_ACTION_OF_SET_VLAN_VID))
> + flow_dev_get_vlan_info_from_items(items,
> &vlan);
> vlan.eth_proto = rte_be_to_cpu_16
> ((((const struct rte_flow_action_of_push_vlan *)
> actions->conf)-
> >ethertype));
> --
> 2.26.0
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2020-04-15 15:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 10:21 [dpdk-dev] [PATCH] " Xiaoyu Min
2020-04-13 3:29 ` [dpdk-dev] [PATCH v2] " Xiaoyu Min
2020-04-15 15:35 ` Raslan Darawsheh [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AM0PR05MB6707ACB34F7E56964AB78B38C2DB0@AM0PR05MB6707.eurprd05.prod.outlook.com \
--to=rasland@mellanox.com \
--cc=dekelp@mellanox.com \
--cc=dev@dpdk.org \
--cc=jackmin@mellanox.com \
--cc=matan@mellanox.com \
--cc=shahafs@mellanox.com \
--cc=stable@dpdk.org \
--cc=viacheslavo@mellanox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).