From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH] test: fbk hash - fix errors with large nb entries
Date: Fri, 17 Oct 2014 14:18:12 +0100 [thread overview]
Message-ID: <1413551892-12573-1-git-send-email-bruce.richardson@intel.com> (raw)
The four-byte-key (fbk) autotest was allocating the keys to be used for
the test on the stack. When the number of entries in the table was
increased significantly, for example, to test larger hashes by increase the
value of ENTRIES, this array of keys was greater than that
allowed on the stack, and so caused problems, i.e. crashes and core dumps.
The solution is to have the keys dynamically allocated on the heap using
malloc. Now if ENTRIES is increased and we run out of memory we get an
error message instead of a crash.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
---
app/test/test_hash_perf.c | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/app/test/test_hash_perf.c b/app/test/test_hash_perf.c
index 7bb7016..be34957 100644
--- a/app/test/test_hash_perf.c
+++ b/app/test/test_hash_perf.c
@@ -397,6 +397,7 @@ struct tbl_perf_test_params tbl_perf_params[] =
if (cond) { \
printf("ERROR line %d: " str "\n", __LINE__, ##__VA_ARGS__); \
if (handle) rte_fbk_hash_free(handle); \
+ if (keys) rte_free(keys); \
return -1; \
} \
} while(0)
@@ -697,8 +698,8 @@ fbk_hash_perf_test(void)
.entries_per_bucket = 4,
.socket_id = rte_socket_id(),
};
- struct rte_fbk_hash_table *handle;
- uint32_t keys[ENTRIES] = {0};
+ struct rte_fbk_hash_table *handle = NULL;
+ uint32_t *keys = NULL;
unsigned indexes[TEST_SIZE];
uint64_t lookup_time = 0;
unsigned added = 0;
@@ -708,6 +709,10 @@ fbk_hash_perf_test(void)
handle = rte_fbk_hash_create(¶ms);
RETURN_IF_ERROR_FBK(handle == NULL, "fbk hash creation failed");
+ keys = rte_zmalloc(NULL, ENTRIES * sizeof(*keys), 0);
+ RETURN_IF_ERROR_FBK(keys == NULL,
+ "fbk hash: memory allocation for key store failed");
+
/* Generate random keys and values. */
for (i = 0; i < ENTRIES; i++) {
uint32_t key = (uint32_t)rte_rand();
--
1.9.3
next reply other threads:[~2014-10-17 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 13:18 Bruce Richardson [this message]
2014-10-20 12:32 ` De Lara Guarch, Pablo
[not found] <1413545645-29168-1-git-send-email-y>
2014-10-17 11:38 ` Bruce Richardson
2014-10-17 11:49 ` Bruce Richardson
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=1413551892-12573-1-git-send-email-bruce.richardson@intel.com \
--to=bruce.richardson@intel.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).