From: Suanming Mou <suanmingm@mellanox.com>
To: matan@mellanox.com, viacheslavo@mellanox.com
Cc: ferruh.yigit@intel.com, rasland@mellanox.com, dev@dpdk.org
Subject: [dpdk-dev] [PATCH] net/mlx5: fix indexed pool 32-bits build error
Date: Sat, 18 Apr 2020 09:44:52 +0800 [thread overview]
Message-ID: <1587174292-201940-1-git-send-email-suanmingm@mellanox.com> (raw)
Currently, 32-bits compiler treats int64_t as long long int different
with 64-bits. The indexed pool dump function build will be failed in
32-bits mode.
As the maximum supported entries of the indexed pool is UINT32_MAX, use
the 64 bits to record the pool statistics is waste of memory. Align the
statistics value type to uint32_t.
Fixes: 1702f7848f6a ("net/mlx5: add indexed memory pool")
Signed-off-by: Suanming Mou <suanmingm@mellanox.com>
---
drivers/net/mlx5/mlx5_utils.c | 4 ++--
drivers/net/mlx5/mlx5_utils.h | 10 +++++-----
2 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/net/mlx5/mlx5_utils.c b/drivers/net/mlx5/mlx5_utils.c
index 7683167..07a6283 100644
--- a/drivers/net/mlx5/mlx5_utils.c
+++ b/drivers/net/mlx5/mlx5_utils.c
@@ -472,8 +472,8 @@ struct mlx5_indexed_pool *
pool->cfg.type, pool->cfg.size, pool->n_trunk_valid,
pool->cfg.trunk_size, pool->n_trunk_valid);
#ifdef POOL_DEBUG
- printf("Pool %s entry %ld, trunk alloc %ld, empty: %ld, "
- "available %ld free %ld\n",
+ printf("Pool %s entry %u, trunk alloc %u, empty: %u, "
+ "available %u free %u\n",
pool->cfg.type, pool->n_entry, pool->trunk_new,
pool->trunk_empty, pool->trunk_avail, pool->trunk_free);
#endif
diff --git a/drivers/net/mlx5/mlx5_utils.h b/drivers/net/mlx5/mlx5_utils.h
index 1051b12..d81ace3 100644
--- a/drivers/net/mlx5/mlx5_utils.h
+++ b/drivers/net/mlx5/mlx5_utils.h
@@ -127,11 +127,11 @@ struct mlx5_indexed_pool {
struct mlx5_indexed_trunk **trunks;
uint32_t free_list; /* Index to first free trunk. */
#ifdef POOL_DEBUG
- int64_t n_entry;
- int64_t trunk_new;
- int64_t trunk_avail;
- int64_t trunk_empty;
- int64_t trunk_free;
+ uint32_t n_entry;
+ uint32_t trunk_new;
+ uint32_t trunk_avail;
+ uint32_t trunk_empty;
+ uint32_t trunk_free;
#endif
uint32_t grow_tbl[]; /* Save the index offset for the grow trunks. */
};
--
1.8.3.1
next reply other threads:[~2020-04-18 1:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-18 1:44 Suanming Mou [this message]
2020-04-19 11:12 ` Raslan Darawsheh
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=1587174292-201940-1-git-send-email-suanmingm@mellanox.com \
--to=suanmingm@mellanox.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=matan@mellanox.com \
--cc=rasland@mellanox.com \
--cc=viacheslavo@mellanox.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).