From: Raslan Darawsheh <rasland@mellanox.com>
To: Suanming Mou <suanmingm@mellanox.com>,
Matan Azrad <matan@mellanox.com>,
Shahaf Shuler <shahafs@mellanox.com>,
Slava Ovsiienko <viacheslavo@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"xiangxia.m.yue@gmail.com" <xiangxia.m.yue@gmail.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix meter header modify before decap issue
Date: Wed, 12 Feb 2020 15:03:11 +0000 [thread overview]
Message-ID: <AM0PR05MB6707EBB93A37426BFD0255B8C21B0@AM0PR05MB6707.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1580962467-159286-1-git-send-email-suanmingm@mellanox.com>
Hi,
> -----Original Message-----
> From: Suanming Mou <suanmingm@mellanox.com>
> Sent: Thursday, February 6, 2020 6:14 AM
> To: Matan Azrad <matan@mellanox.com>; Shahaf Shuler
> <shahafs@mellanox.com>; Slava Ovsiienko <viacheslavo@mellanox.com>
> Cc: dev@dpdk.org; xiangxia.m.yue@gmail.com; Raslan Darawsheh
> <rasland@mellanox.com>; stable@dpdk.org
> Subject: [PATCH] net/mlx5: fix meter header modify before decap issue
>
> The meter flows are split into three subflows each, the prefix subflow
> with meter action color the packet, the meter subflow filters out the
> colored packets, the suffix subflow applies all the remaining actions
> to the passed packets. The tag header modify action is added to the
> prefix subflow to make the suffix subflow to match the packets from the
> prefix subflow.
>
> Currently, the tag header modify action is added at the beginning in the
> prefix subflow even before decap action. The header modify action does
> not make sense to the later decap action, so the flow create will be
> validated as incorrect flow rule and failed.
>
> Move the tag header modify action just before meter action in the prefix
> subflow to make the flow with decap action to do the decap first, then
> do the tag and meter to fix that issue.
>
> Fixes: 9ea9b049a960 ("net/mlx5: split meter flow")
> Cc: stable@dpdk.org
>
> Reported-by: Tonghao Zhang <xiangxia.m.yue@gmail.com>
> Signed-off-by: Suanming Mou <suanmingm@mellanox.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
> ---
> drivers/net/mlx5/mlx5_flow.c | 15 ++++++++++-----
> 1 file changed, 10 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/net/mlx5/mlx5_flow.c b/drivers/net/mlx5/mlx5_flow.c
> index 144e07c..7f1830f 100644
> --- a/drivers/net/mlx5/mlx5_flow.c
> +++ b/drivers/net/mlx5/mlx5_flow.c
> @@ -3476,21 +3476,25 @@ uint32_t mlx5_flow_adjust_priority(struct
> rte_eth_dev *dev, int32_t priority,
> struct rte_flow_action actions_sfx[],
> struct rte_flow_action actions_pre[])
> {
> - struct rte_flow_action *tag_action;
> + struct rte_flow_action *tag_action = NULL;
> struct mlx5_rte_flow_action_set_tag *set_tag;
> struct rte_flow_error error;
> const struct rte_flow_action_raw_encap *raw_encap;
> const struct rte_flow_action_raw_decap *raw_decap;
> uint32_t tag_id;
>
> - /* Add the extra tag action first. */
> - tag_action = actions_pre;
> - tag_action->type = MLX5_RTE_FLOW_ACTION_TYPE_TAG;
> - actions_pre++;
> /* Prepare the actions for prefix and suffix flow. */
> for (; actions->type != RTE_FLOW_ACTION_TYPE_END; actions++) {
> switch (actions->type) {
> case RTE_FLOW_ACTION_TYPE_METER:
> + /* Add the extra tag action first. */
> + tag_action = actions_pre;
> + tag_action->type =
> MLX5_RTE_FLOW_ACTION_TYPE_TAG;
> + actions_pre++;
> + memcpy(actions_pre, actions,
> + sizeof(struct rte_flow_action));
> + actions_pre++;
> + break;
> case RTE_FLOW_ACTION_TYPE_VXLAN_DECAP:
> case RTE_FLOW_ACTION_TYPE_NVGRE_DECAP:
> memcpy(actions_pre, actions,
> @@ -3545,6 +3549,7 @@ uint32_t mlx5_flow_adjust_priority(struct
> rte_eth_dev *dev, int32_t priority,
> */
> tag_id = flow_qrss_get_id(dev);
> set_tag->data = tag_id << MLX5_MTR_COLOR_BITS;
> + assert(tag_action);
> tag_action->conf = set_tag;
> return tag_id;
> }
> --
> 1.8.3.1
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2020-02-12 15:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 4:14 Suanming Mou
2020-02-12 14:13 ` Matan Azrad
2020-02-12 15:03 ` 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=AM0PR05MB6707EBB93A37426BFD0255B8C21B0@AM0PR05MB6707.eurprd05.prod.outlook.com \
--to=rasland@mellanox.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
--cc=shahafs@mellanox.com \
--cc=stable@dpdk.org \
--cc=suanmingm@mellanox.com \
--cc=viacheslavo@mellanox.com \
--cc=xiangxia.m.yue@gmail.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).