From: laijs@cn.fujitsu.com (Lai Jiangshan)
Subject: [ltt-dev] [PATCH 9/9] change strategy for AR_RANDOM
Date: Mon, 14 Nov 2011 12:50:59 +0800 [thread overview]
Message-ID: <1321246259-21223-10-git-send-email-laijs@cn.fujitsu.com> (raw)
In-Reply-To: <1321246259-21223-1-git-send-email-laijs@cn.fujitsu.com>
Signed-off-by: Lai Jiangshan <laijs at cn.fujitsu.com>
---
tests/test_urcu_hash.c | 34 ++++++++++++++++++++++++++++++++--
1 files changed, 32 insertions(+), 2 deletions(-)
diff --git a/tests/test_urcu_hash.c b/tests/test_urcu_hash.c
index 964a4e1..f07f0d4 100644
--- a/tests/test_urcu_hash.c
+++ b/tests/test_urcu_hash.c
@@ -540,6 +540,37 @@ void free_node_cb(struct rcu_head *head)
free(node);
}
+static inline
+int thr_writer_add(void)
+{
+ static __thread int addremove_thread;
+ unsigned addremove_random;
+
+ if (add_only)
+ return 1;
+
+ if (addremove == AR_ADD)
+ return 1;
+
+ if (addremove == AR_REMOVE)
+ return 0;
+
+ addremove_random = test_rand_get_bits(2);
+ if (addremove_random < 2)
+ return addremove_random;
+
+ while (caa_unlikely(!addremove_thread))
+ addremove_thread = test_rand_get_bits(16) - (1UL << 15);
+
+ if (addremove_thread > 0) {
+ addremove_thread--;
+ return 1;
+ } else {
+ addremove_thread++;
+ return 0;
+ }
+}
+
void *thr_writer(void *_count)
{
struct lfht_test_node *node;
@@ -562,8 +593,7 @@ void *thr_writer(void *_count)
cmm_smp_mb();
for (;;) {
- if ((addremove == AR_ADD || add_only)
- || (addremove == AR_RANDOM && test_rand_get_bits(1))) {
+ if (thr_writer_add()) {
node = malloc(sizeof(struct lfht_test_node));
lfht_test_node_init(node);
rcu_read_lock();
--
1.7.4.4
next prev parent reply other threads:[~2011-11-14 4:50 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 4:50 [ltt-dev] [PATCH 0/9] change lfht test Lai Jiangshan
2011-11-14 4:50 ` [ltt-dev] [PATCH 1/9] Fix arguments order Lai Jiangshan
2011-11-14 12:57 ` Mathieu Desnoyers
2011-11-14 4:50 ` [ltt-dev] [PATCH 2/9] keep the last position for failed lookup Lai Jiangshan
2011-11-15 11:10 ` Mathieu Desnoyers
2011-11-16 8:33 ` Lai Jiangshan
2011-11-14 4:50 ` [ltt-dev] [PATCH 3/9] add cds_lfht_add_at() Lai Jiangshan
2011-11-15 8:23 ` Lai Jiangshan
2011-11-15 11:07 ` Mathieu Desnoyers
2011-11-18 14:29 ` Mathieu Desnoyers
2011-11-21 3:15 ` Lai Jiangshan
2011-11-22 9:41 ` Mathieu Desnoyers
2011-11-14 4:50 ` [ltt-dev] [PATCH 4/9] new random generator Lai Jiangshan
2011-11-15 11:17 ` Mathieu Desnoyers
2011-11-14 4:50 ` [ltt-dev] [PATCH 5/9] use random value for hash value directly Lai Jiangshan
2011-11-15 11:20 ` Mathieu Desnoyers
2011-11-16 8:41 ` Lai Jiangshan
2011-11-14 4:50 ` [ltt-dev] [PATCH 6/9] test hash value Confilict with buckets Lai Jiangshan
2011-11-15 11:22 ` Mathieu Desnoyers
2011-11-16 8:53 ` Lai Jiangshan
2011-11-14 4:50 ` [ltt-dev] [PATCH 7/9] add identical-hash-value-chain test Lai Jiangshan
2011-11-15 11:24 ` Mathieu Desnoyers
2011-11-16 8:55 ` Lai Jiangshan
2011-11-14 4:50 ` [ltt-dev] [PATCH 8/9] add duplicated node test Lai Jiangshan
2011-11-15 11:31 ` Mathieu Desnoyers
2011-11-16 9:16 ` Lai Jiangshan
2011-11-14 4:50 ` Lai Jiangshan [this message]
2011-11-15 11:35 ` [ltt-dev] [PATCH 9/9] change strategy for AR_RANDOM Mathieu Desnoyers
2011-11-16 9:26 ` Lai Jiangshan
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=1321246259-21223-10-git-send-email-laijs@cn.fujitsu.com \
--to=laijs@cn.fujitsu.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