From: anik.mishra@ericsson.com (Anik Mishra)
Subject: [lttng-dev] [RFC PATCH lttng-ust] Introduce hash table for lttng_create_event_if_missing()
Date: Wed, 16 Jan 2013 21:37:32 +0000 [thread overview]
Message-ID: <0AF7BA51953555439020FD85D854801F039A5D@eusaamb105.ericsson.se> (raw)
-----Original Message-----
From: Mathieu Desnoyers [mailto:mathieu.desnoyers@efficios.com]
Sent: January-16-13 10:15 AM
To: lttng-dev at lists.lttng.org
Subject: [lttng-dev] [RFC PATCH lttng-ust] Introduce hash table for lttng_create_event_if_missing()
[...]
@@ -329,17 +331,19 @@ int lttng_event_create(const struct lttng_event_desc *desc, {
[...]
- /*
- * This is O(n^2) (for each event, the loop is called at event
- * creation). Might require a hash if we have lots of events.
- */
- cds_list_for_each_entry(event, &chan->session->events_head, node) {
+ hash = jhash(event_name, name_len, 0);
+ head = &chan->session->events_ht.table[hash & (LTTNG_UST_EVENT_HT_SIZE - 1)];
+ cds_hlist_for_each_entry(event, node, head, hlist) {
[...]
From other code:
#define LTTNG_UST_EVENT_HT_BITS 6
#define LTTNG_UST_EVENT_HT_SIZE (1U << LTTNG_UST_EVENT_HT_BITS)
The way I read this, if there's a substantial number of events, you're just dividing the time required by a constant 64. The complexity remains the same. Are you sure this is really a long term solution?
Anik
next reply other threads:[~2013-01-16 21:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 21:37 Anik Mishra [this message]
2013-01-21 19:06 ` Mathieu Desnoyers
-- strict thread matches above, loose matches on Subject: below --
2013-01-16 15:14 Mathieu Desnoyers
2013-01-16 15:53 ` David Goulet
2013-01-16 16:19 ` Christian Babeux
2013-01-16 17:58 ` Mathieu Desnoyers
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=0AF7BA51953555439020FD85D854801F039A5D@eusaamb105.ericsson.se \
--to=anik.mishra@ericsson.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