From: Andre Muezerie <andremue@linux.microsoft.com>
To: andremue@linux.microsoft.com
Cc: bruce.richardson@intel.com, dev@dpdk.org,
sameh.gobriel@intel.com, vladimir.medvedkin@intel.com,
yipeng1.wang@intel.com
Subject: [PATCH v5 0/3] fix how large numbers are printed by hash tests
Date: Tue, 8 Apr 2025 18:20:55 -0700 [thread overview]
Message-ID: <1744161658-7874-1-git-send-email-andremue@linux.microsoft.com> (raw)
In-Reply-To: <1741291408-26509-1-git-send-email-andremue@linux.microsoft.com>
v5:
- Rebased and updated to conform to new function versioning mechanism.
v4:
- Added parameter "unit", which allows rte_size_to_str() to be smarter
about the need to append a space after the number. This keeps the
function easy to use and avoids the need for complex explanations
about the space that could be needed between number and multiple/unit.
- Changed the return type of rte_size_to_str() to be buf, or NULL on
error, allowing the function to be inlined.
- Removed a line wrap.
v3:
- Added rte_size_to_str to version.map (marked experimental for 25.07) so
that symbol gets exported when building with -Ddefault_library=shared
- Added sample outputs
- Added a space between the number and the postfix (if a postfix is
present)
Andre Muezerie (3):
eal: add function rte_size_to_str
hash_multiwriter_autotest: fix printf parameters
hash_readwrite_autotest: fix printf parameters
app/test/test_hash_multiwriter.c | 14 +++++--
app/test/test_hash_readwrite.c | 14 ++++++-
lib/eal/common/eal_common_string_fns.c | 54 ++++++++++++++++++++++++++
lib/eal/include/rte_common.h | 34 ++++++++++++++++
4 files changed, 111 insertions(+), 5 deletions(-)
--
2.49.0.vfs.0.0
next prev parent reply other threads:[~2025-04-09 1:21 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 20:03 [PATCH] hash_readwrite_autotest: fix printf parameters Andre Muezerie
2025-03-07 9:01 ` Bruce Richardson
2025-03-07 22:34 ` Andre Muezerie
2025-03-10 10:51 ` Bruce Richardson
2025-03-10 15:36 ` Stephen Hemminger
2025-03-11 14:39 ` Andre Muezerie
2025-03-11 15:01 ` Morten Brørup
2025-03-11 15:33 ` [PATCH v2 1/3] eal: add function rte_size_to_str Andre Muezerie
2025-03-11 15:33 ` [PATCH v2 2/3] hash_multiwriter_autotest: fix printf parameters Andre Muezerie
2025-03-11 15:33 ` [PATCH v2 3/3] hash_readwrite_autotest: " Andre Muezerie
2025-03-11 15:49 ` [PATCH v2 1/3] eal: add function rte_size_to_str Stephen Hemminger
2025-03-11 15:51 ` Bruce Richardson
2025-03-11 16:21 ` Morten Brørup
2025-03-12 19:28 ` [PATCH v3 0/3] fix how large numbers are printed by hash tests Andre Muezerie
2025-03-12 19:28 ` [PATCH v3 1/3] eal: add function rte_size_to_str Andre Muezerie
2025-03-13 9:09 ` Bruce Richardson
2025-03-13 10:07 ` Morten Brørup
2025-03-13 10:35 ` Bruce Richardson
2025-03-14 11:56 ` Mattias Rönnblom
2025-03-13 10:41 ` Bruce Richardson
2025-03-13 14:06 ` Andre Muezerie
2025-03-12 19:28 ` [PATCH v3 2/3] hash_multiwriter_autotest: fix printf parameters Andre Muezerie
2025-03-12 19:28 ` [PATCH v3 3/3] hash_readwrite_autotest: " Andre Muezerie
2025-03-13 16:51 ` [PATCH v4 0/3] fix how large numbers are printed by hash tests Andre Muezerie
2025-03-13 16:51 ` [PATCH v4 1/3] eal: add function rte_size_to_str Andre Muezerie
2025-03-13 16:59 ` Morten Brørup
2025-03-13 16:51 ` [PATCH v4 2/3] hash_multiwriter_autotest: fix printf parameters Andre Muezerie
2025-03-13 16:51 ` [PATCH v4 3/3] hash_readwrite_autotest: " Andre Muezerie
2025-03-13 17:33 ` [PATCH v4 0/3] fix how large numbers are printed by hash tests Bruce Richardson
2025-04-09 1:20 ` Andre Muezerie [this message]
2025-04-09 1:20 ` [PATCH v5 1/3] eal: add function rte_size_to_str Andre Muezerie
2025-04-09 1:20 ` [PATCH v5 2/3] hash_multiwriter_autotest: fix printf parameters Andre Muezerie
2025-04-09 1:20 ` [PATCH v5 3/3] hash_readwrite_autotest: " Andre Muezerie
2025-04-10 11:34 ` [PATCH v5 0/3] fix how large numbers are printed by hash tests David Marchand
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=1744161658-7874-1-git-send-email-andremue@linux.microsoft.com \
--to=andremue@linux.microsoft.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=sameh.gobriel@intel.com \
--cc=vladimir.medvedkin@intel.com \
--cc=yipeng1.wang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.