From: Dariusz Sosnowski <dsosnowski@nvidia.com>
To: Khadem Ullah <14pwcse1224@uetpeshawar.edu.pk>
Cc: Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>,
Matan Azrad <matan@nvidia.com>, <dev@dpdk.org>, <stable@dpdk.org>
Subject: Re: [PATCH v3] net/mlx5: fix connection tracking state item validation
Date: Thu, 14 Aug 2025 11:33:50 +0200 [thread overview]
Message-ID: <20250814093350.5ecaiakzdgvfjbwk@ds-vm-debian.local> (raw)
In-Reply-To: <20250814085831.3511020-1-14pwcse1224@uetpeshawar.edu.pk>
On Thu, Aug 14, 2025 at 04:58:31AM -0400, Khadem Ullah wrote:
> [ snip ]
>
> +#define MLX5_FLOW_CONNTRACK_PKT_STATE_ALL(flags_all) \
> + (flags_all = (RTE_FLOW_CONNTRACK_PKT_STATE_VALID) | \
> + RTE_FLOW_CONNTRACK_PKT_STATE_CHANGED | \
> + RTE_FLOW_CONNTRACK_PKT_STATE_INVALID | \
> + RTE_FLOW_CONNTRACK_PKT_STATE_DISABLED | \
> + RTE_FLOW_CONNTRACK_PKT_STATE_BAD)
Please define this macro without setting the variable.
It should define only the constant value.
Defining this macro as proposed requires the user of that macro
to declare a variable, which is not needed for comparison against item's flags.
I mean something like this:
if (spec->flags & ~MLX5_FLOW_CONNTRACK_PKT_STATE_ALL)
If macro is defined in the fashion allowing that,
the flags_all variable definition will not be needed.
Could you also please add an empty line between the macro definition and
the comment appearing after it, so they appear separated?
> /*
> * When HW steering flow engine is used, the CT action handles are encoded in a following way:
> * - bits 31:29 - type
>
> [ snip ]
Best regards,
Dariusz Sosnowski
next prev parent reply other threads:[~2025-08-14 9:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 13:23 [PATCH] " Khadem Ullah
2025-08-05 14:44 ` Ivan Malov
2025-08-06 8:51 ` Khadem Ullah
2025-08-08 7:47 ` Dariusz Sosnowski
2025-08-11 6:21 ` Khadem Ullah
2025-08-11 15:15 ` Dariusz Sosnowski
2025-08-11 16:27 ` Khadem Ullah
2025-08-11 17:18 ` Dariusz Sosnowski
2025-08-12 9:51 ` Dariusz Sosnowski
2025-08-12 12:50 ` Khadem Ullah
2025-08-12 12:46 ` [PATCH v2] " Khadem Ullah
2025-08-13 14:16 ` Dariusz Sosnowski
2025-08-14 9:06 ` Khadem Ullah
2025-08-14 8:58 ` [PATCH v3] " Khadem Ullah
2025-08-14 9:33 ` Dariusz Sosnowski [this message]
2025-08-14 10:20 ` Khadem Ullah
2025-08-14 10:16 ` [PATCH v4] " Khadem Ullah
2025-08-14 11:43 ` Dariusz Sosnowski
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=20250814093350.5ecaiakzdgvfjbwk@ds-vm-debian.local \
--to=dsosnowski@nvidia.com \
--cc=14pwcse1224@uetpeshawar.edu.pk \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=stable@dpdk.org \
--cc=suanmingm@nvidia.com \
--cc=viacheslavo@nvidia.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).