From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [ltt-dev] [PATCH 2/9] keep the last position for failed lookup
Date: Tue, 15 Nov 2011 06:10:31 -0500 [thread overview]
Message-ID: <20111115111031.GB16701@Krystal> (raw)
In-Reply-To: <1321246259-21223-3-git-send-email-laijs@cn.fujitsu.com>
* Lai Jiangshan (laijs at cn.fujitsu.com) wrote:
> Signed-off-by: Lai Jiangshan <laijs at cn.fujitsu.com>
> ---
> rculfhash.c | 19 +++++++++++--------
> tests/test_urcu_hash.c | 5 +++--
> urcu/rculfhash.h | 17 +++++++++++------
> 3 files changed, 25 insertions(+), 16 deletions(-)
>
> diff --git a/rculfhash.c b/rculfhash.c
> index bda3bd6..cbfc79e 100644
> --- a/rculfhash.c
> +++ b/rculfhash.c
> @@ -1381,27 +1381,28 @@ struct cds_lfht *_cds_lfht_new(unsigned long init_size,
> return ht;
> }
>
> -void cds_lfht_lookup(struct cds_lfht *ht, unsigned long hash,
> +bool cds_lfht_lookup(struct cds_lfht *ht, unsigned long hash,
> cds_lfht_match_fct match, void *key,
> struct cds_lfht_iter *iter)
> {
[...]
> #define cds_lfht_for_each_duplicate(ht, hash, match, key, iter, node) \
> - for (cds_lfht_lookup(ht, hash, match, key, iter), \
> - node = cds_lfht_iter_get_node(iter); \
> + for (node = cds_lfht_lookup(ht, hash, match, key, iter) ? \
> + cds_lfht_iter_get_node(iter) : NULL; \
Hrm, is it me or this just complexifies use of this API ? Now, instead
of a
cds_lfht_lookup -> cds_lfht_iter_get_node -> check for null
chain, we need to do:
cds_lfht_lookup -> check for nonzero return ? cds_lfht_iter_get_node :
NULL -> check for NULL
actually adding one test into the caller code.
What use-case is it allowing to justify this added API complexity ?
Thanks,
Mathieu
> node != NULL; \
> cds_lfht_next_duplicate(ht, match, key, iter), \
> node = cds_lfht_iter_get_node(iter))
> @@ -391,8 +395,9 @@ void cds_lfht_resize(struct cds_lfht *ht, unsigned long new_size);
>
> #define cds_lfht_for_each_entry_duplicate(ht, hash, match, key, \
> iter, pos, member) \
> - for (cds_lfht_lookup(ht, hash, match, key, iter), \
> - pos = caa_container_of(cds_lfht_iter_get_node(iter), \
> + for (pos = caa_container_of( \
> + cds_lfht_lookup(ht, hash, match, key, iter) ? \
> + cds_lfht_iter_get_node(iter) : NULL, \
> typeof(*(pos)), member); \
> &(pos)->member != NULL; \
> cds_lfht_next_duplicate(ht, match, key, iter), \
> --
> 1.7.4.4
>
--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2011-11-15 11:10 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 [this message]
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 ` [ltt-dev] [PATCH 9/9] change strategy for AR_RANDOM Lai Jiangshan
2011-11-15 11:35 ` 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=20111115111031.GB16701@Krystal \
--to=mathieu.desnoyers@efficios.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