From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [lttng-dev] Do updaters of a cds_lfht need to be synchronized?
Date: Mon, 31 Oct 2016 15:50:45 +0000 (UTC) [thread overview]
Message-ID: <1821874660.10064.1477929045393.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <MWHPR11MB17756EC0046E84C041DF022398AD0@MWHPR11MB1775.namprd11.prod.outlook.com>
----- On Oct 28, 2016, at 11:40 AM, Charles Jacobsen <charles.jacobsen at primarydata.com> wrote:
> The documentation for the lock-free hash table does not mention anything about
> synchronizing updaters (e.g., with a lock):
> [ https://lwn.net/Articles/573431/ | https://lwn.net/Articles/573431/ ]
> [ https://lwn.net/Articles/573432/ | https://lwn.net/Articles/573432/ ]
> The source for rculfhash (== cds_lfht?) also mentions in the comments that add
> and remove are lock free:
> [ https://github.com/urcu/userspace-rcu/blob/master/src/rculfhash.c |
> https://github.com/urcu/userspace-rcu/blob/master/src/rculfhash.c ]
> Is it safe to assume that cds_lfht_add, cds_lfht_add_unique, and so on, *only*
> require a surrounding rcu read lock/unlock?
> "lock free" is part of the name, so I would assume the answer is "yes".
Yes, this assumption is correct.
Thanks,
Mathieu
> Thank you.
> Disclaimer
> The information contained in this communication from the sender is confidential.
> It is intended solely for use by the recipient and others authorized to receive
> it. If you are not the recipient, you are hereby notified that any disclosure,
> copying, distribution or taking action in relation of the contents of this
> information is strictly prohibited and may be unlawful.
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.lttng.org/pipermail/lttng-dev/attachments/20161031/8b0a2774/attachment.html>
next prev parent reply other threads:[~2016-10-31 15:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 15:40 Charles Jacobsen
2016-10-31 15:50 ` Mathieu Desnoyers [this message]
2016-10-31 16:01 ` Charles Jacobsen
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=1821874660.10064.1477929045393.JavaMail.zimbra@efficios.com \
--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