From: Maayan Kashani <mkashani@nvidia.com>
To: Andre Muezerie <andremue@linux.microsoft.com>,
Dariusz Sosnowski <dsosnowski@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>,
Matan Azrad <matan@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH] net/mlx5: declare size of rte_v128u32_t
Date: Sun, 25 May 2025 08:47:31 +0000 [thread overview]
Message-ID: <PH7PR12MB7018AF2B11C04F5B177B3568B29AA@PH7PR12MB7018.namprd12.prod.outlook.com> (raw)
In-Reply-To: <1746457823-11135-1-git-send-email-andremue@linux.microsoft.com>
Hi, Andre,
Thanks for your contribution and patches,
This fix should be handled diff and not by const,
as the typedef might change in future and the const value will stay and cause a bug.
Regards,
Maayan Kashani
> -----Original Message-----
> From: Andre Muezerie <andremue@linux.microsoft.com>
> Sent: Monday, 5 May 2025 18:10
> To: Dariusz Sosnowski <dsosnowski@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Bing Zhao <bingz@nvidia.com>; Ori Kam
> <orika@nvidia.com>; Suanming Mou <suanmingm@nvidia.com>; Matan
> Azrad <matan@nvidia.com>
> Cc: dev@dpdk.org; Andre Muezerie <andremue@linux.microsoft.com>
> Subject: [PATCH] net/mlx5: declare size of rte_v128u32_t
>
> External email: Use caution opening links or attachments
>
>
> When compiling with MSVC the error below is hit:
>
> drivers\net\mlx5\mlx5_tx.h(1148): error C2065: 'rte_v128u32_t':
> undeclared identifier
>
> Turns out that with MSVC the data type rte_v128u32_t is not used, but its
> size needs to be known. This patch defines a macro to store that size and
> replaces instances of sizeof(rte_v128u32_t) with that macro.
>
> Signed-off-by: Andre Muezerie <andremue@linux.microsoft.com>
> ---
> drivers/net/mlx5/mlx5_defs.h | 2 ++
> drivers/net/mlx5/mlx5_rxtx.c | 6 +++---
> drivers/net/mlx5/mlx5_tx.h | 2 +-
> 3 files changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/net/mlx5/mlx5_defs.h b/drivers/net/mlx5/mlx5_defs.h
> index 9c454983be..c5e2c59309 100644
> --- a/drivers/net/mlx5/mlx5_defs.h
> +++ b/drivers/net/mlx5/mlx5_defs.h
> @@ -196,4 +196,6 @@
>
> #define MLX5_CNT_SVC_CYCLE_TIME_DEFAULT 500
>
> +#define MLX5_SIZEOF_V128U32_T 16
> +
> #endif /* RTE_PMD_MLX5_DEFS_H_ */
> diff --git a/drivers/net/mlx5/mlx5_rxtx.c b/drivers/net/mlx5/mlx5_rxtx.c
> index 9c075f6a56..b30d620f54 100644
> --- a/drivers/net/mlx5/mlx5_rxtx.c
> +++ b/drivers/net/mlx5/mlx5_rxtx.c
> @@ -32,7 +32,7 @@ static_assert(MLX5_CQE_STATUS_HW_OWN < 0, "Must
> be negative value"); static_assert(MLX5_CQE_STATUS_SW_OWN < 0, "Must
> be negative value"); static_assert(MLX5_ESEG_MIN_INLINE_SIZE ==
> (sizeof(uint16_t) +
> - sizeof(rte_v128u32_t)),
> + MLX5_SIZEOF_V128U32_T),
> "invalid Ethernet Segment data size");
> static_assert(MLX5_ESEG_MIN_INLINE_SIZE ==
> (sizeof(uint16_t) +
> @@ -41,7 +41,7 @@ static_assert(MLX5_ESEG_MIN_INLINE_SIZE ==
> "invalid Ethernet Segment data size");
> static_assert(MLX5_ESEG_MIN_INLINE_SIZE ==
> (sizeof(uint16_t) +
> - sizeof(rte_v128u32_t)),
> + MLX5_SIZEOF_V128U32_T),
> "invalid Ethernet Segment data size");
> static_assert(MLX5_ESEG_MIN_INLINE_SIZE ==
> (sizeof(uint16_t) +
> @@ -50,7 +50,7 @@ static_assert(MLX5_ESEG_MIN_INLINE_SIZE ==
> "invalid Ethernet Segment data size");
> static_assert(MLX5_ESEG_MIN_INLINE_SIZE ==
> (sizeof(uint16_t) +
> - sizeof(rte_v128u32_t)),
> + MLX5_SIZEOF_V128U32_T),
> "invalid Ethernet Segment data size");
> static_assert(MLX5_ESEG_MIN_INLINE_SIZE ==
> (sizeof(uint16_t) +
> diff --git a/drivers/net/mlx5/mlx5_tx.h b/drivers/net/mlx5/mlx5_tx.h index
> 55568c41b1..5647f6a37d 100644
> --- a/drivers/net/mlx5/mlx5_tx.h
> +++ b/drivers/net/mlx5/mlx5_tx.h
> @@ -1145,7 +1145,7 @@ mlx5_tx_eseg_data(struct mlx5_txq_data
> *__rte_restrict txq,
> } else {
> /* Fill the gap in the title WQEBB with inline data. */
> rte_mov16(pdst, psrc);
> - psrc += sizeof(rte_v128u32_t);
> + psrc += MLX5_SIZEOF_V128U32_T;
> }
> pdst = (uint8_t *)(es + 2);
> MLX5_ASSERT(inlen >= MLX5_ESEG_MIN_INLINE_SIZE);
> --
> 2.49.0.vfs.0.0
next prev parent reply other threads:[~2025-05-25 8:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 15:10 Andre Muezerie
2025-05-25 8:47 ` Maayan Kashani [this message]
2025-05-31 0:20 ` Andre Muezerie
2025-05-31 0:21 ` [PATCH v2] " Andre Muezerie
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=PH7PR12MB7018AF2B11C04F5B177B3568B29AA@PH7PR12MB7018.namprd12.prod.outlook.com \
--to=mkashani@nvidia.com \
--cc=andremue@linux.microsoft.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--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).