From: Igor Gutorov <igootorov@gmail.com>
To: dev@dpdk.org
Cc: Igor Gutorov <igootorov@gmail.com>
Subject: [PATCH v3 2/2] common/mlx5: reduce HCA attribute type sizes
Date: Wed, 7 Aug 2024 23:44:06 +0300 [thread overview]
Message-ID: <20240807204406.700332-3-igootorov@gmail.com> (raw)
In-Reply-To: <20240807204406.700332-1-igootorov@gmail.com>
A number of `log_max_*` fields' types are unnecessarily large, and can
be reduced to `uint8_t`.
Signed-off-by: Igor Gutorov <igootorov@gmail.com>
---
drivers/common/mlx5/mlx5_devx_cmds.h | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/common/mlx5/mlx5_devx_cmds.h b/drivers/common/mlx5/mlx5_devx_cmds.h
index 2ad9e5414f..f523bf8529 100644
--- a/drivers/common/mlx5/mlx5_devx_cmds.h
+++ b/drivers/common/mlx5/mlx5_devx_cmds.h
@@ -268,10 +268,10 @@ struct mlx5_hca_attr {
struct mlx5_hca_flex_attr flex;
struct mlx5_hca_crypto_mmo_attr crypto_mmo;
uint8_t log_max_wq_sz;
- int log_max_qp_sz;
- int log_max_cq_sz;
- int log_max_qp;
- int log_max_cq;
+ uint8_t log_max_qp_sz;
+ uint8_t log_max_cq_sz;
+ uint8_t log_max_qp;
+ uint8_t log_max_cq;
uint32_t log_max_pd;
uint32_t log_max_mrw_sz;
uint32_t log_max_srq;
--
2.45.2
next prev parent reply other threads:[~2024-08-07 20:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-16 17:38 [PATCH 0/1] net/mlx5: show rx/tx descriptor ring limitations in rte_eth_dev_info Igor Gutorov
2024-06-16 17:38 ` [PATCH 1/1] " Igor Gutorov
2024-06-17 7:18 ` Slava Ovsiienko
2024-06-18 22:56 ` [PATCH v2 0/1] net/mlx5: fix incorrect rx/tx descriptor " Igor Gutorov
2024-06-18 22:56 ` [PATCH v2] " Igor Gutorov
2024-06-23 11:34 ` [PATCH v2 0/1] " Slava Ovsiienko
2024-08-07 20:44 ` [PATCH v3 0/2] net/mlx5: fix reported Rx/Tx desc limits Igor Gutorov
2024-08-07 20:44 ` [PATCH v3 1/2] " Igor Gutorov
2024-08-07 20:44 ` Igor Gutorov [this message]
2024-08-07 20:58 ` [PATCH v3 0/2] " Igor Gutorov
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=20240807204406.700332-3-igootorov@gmail.com \
--to=igootorov@gmail.com \
--cc=dev@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).