DPDK usage discussions
 help / color / mirror / Atom feed
From: Suanming Mou <suanmingm@nvidia.com>
To: Guvenc Gulce <guvenc.gulce@gmail.com>,
	"users@dpdk.org" <users@dpdk.org>,
	 Gregory Etelson <getelson@nvidia.com>
Cc: Ori Kam <orika@nvidia.com>, Maayan Kashani <mkashani@nvidia.com>
Subject: RE: mlx5: rte_flow template/async API raw_encap validation bug ?
Date: Tue, 19 Mar 2024 00:24:09 +0000	[thread overview]
Message-ID: <CO6PR12MB53969FC75835335A9F32DB68C12C2@CO6PR12MB5396.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CAK198Oavi=SHGV09k0dF4cmaVsmPnyN=qz84=rgB5Q8UV5-2+A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2816 bytes --]

Hi Guvenc,

From: Guvenc Gulce <guvenc.gulce@gmail.com>
Sent: Monday, March 18, 2024 6:26 PM
To: users@dpdk.org
Cc: Suanming Mou <suanmingm@nvidia.com>; Ori Kam <orika@nvidia.com>
Subject: mlx5: rte_flow template/async API raw_encap validation bug ?

Hi all,

It is great that we have rte_flow async/template api integrated to mlx5
driver code and it is being established as the new standard rte_flow API.

I have the following raw_encap problem when using the rte_flow async/template API
with mlx5 driver:
- raw_encap rte_flow action template fails during validation when the action mask
conf is NULL but this clearly contradicts the explanation from Suanming Mou's
commit 7f6daa490d9 which clearly states that the raw encap action mask is allowed
to be NULL.
<Excerpt from commit 7f6daa490d9>
    2. RAW encap (encap_data: raw)
            action conf (raw_data)

            a. action mask conf (not NULL)
              - encap_data constant.
            b. action mask conf (NULL)
              - encap_data will change.
</Excerpt from commit 7f6daa490d9>

Commenting out the raw_encap validation would make it possible to create
rte_flow template with null mask conf which can be concretized later on.
Things seem to work after relaxing the rte_flow raw_encap validation.
The change would look like:

[Suanming] I guess maybe it is due to the raw_encap and raw_decap combination. I added Gregory who added that code maybe can explain it better. @Gregory Etelson<mailto:getelson@nvidia.com>

<Excerpt>
diff --git a/drivers/net/mlx5/mlx5_flow_hw.c b/drivers/net/mlx5/mlx5_flow_hw.c
index 35f1ed7a03..3f57fd9286 100644
--- a/drivers/net/mlx5/mlx5_flow_hw.c
+++ b/drivers/net/mlx5/mlx5_flow_hw.c
@@ -6020,10 +6020,10 @@ flow_hw_validate_action_raw_encap(const struct rte_flow_action *action,
        const struct rte_flow_action_raw_encap *mask_conf = mask->conf;
        const struct rte_flow_action_raw_encap *action_conf = action->conf;

-       if (!mask_conf || !mask_conf->size)
+/*     if (!mask_conf || !mask_conf->size)
                return rte_flow_error_set(error, EINVAL,
                                          RTE_FLOW_ERROR_TYPE_ACTION, mask,
-                                         "raw_encap: size must be masked");
+                                         "raw_encap: size must be masked"); */
        if (!action_conf || !action_conf->size)
                return rte_flow_error_set(error, EINVAL,
                                          RTE_FLOW_ERROR_TYPE_ACTION, action,
</Excerpt>

But this can not be the proper solution. Please advise a solution how to make the
raw_encap work with rte_flow template/async API. If relaxing the validation is ok, I can
also prepare and send a patch.

Thanks in advance,

Guvenc Gulce


[-- Attachment #2: Type: text/html, Size: 9692 bytes --]

  reply	other threads:[~2024-03-19  0:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-18 10:26 Guvenc Gulce
2024-03-19  0:24 ` Suanming Mou [this message]
2024-03-19 14:25   ` Gregory Etelson
2024-03-20 15:19     ` Tao Li
2024-03-20 16:36       ` Gregory Etelson
2024-03-21  9:28         ` Tao Li

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=CO6PR12MB53969FC75835335A9F32DB68C12C2@CO6PR12MB5396.namprd12.prod.outlook.com \
    --to=suanmingm@nvidia.com \
    --cc=getelson@nvidia.com \
    --cc=guvenc.gulce@gmail.com \
    --cc=mkashani@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=users@dpdk.org \
    /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).