Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: charles.jacobsen@primarydata.com (Charles Jacobsen)
Subject: [lttng-dev] Do updaters of a cds_lfht need to be synchronized?
Date: Fri, 28 Oct 2016 15:40:28 +0000	[thread overview]
Message-ID: <MWHPR11MB17756EC0046E84C041DF022398AD0@MWHPR11MB1775.namprd11.prod.outlook.com> (raw)

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/


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


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".


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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.lttng.org/pipermail/lttng-dev/attachments/20161028/8260b328/attachment.html>


             reply	other threads:[~2016-10-28 15:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-28 15:40 Charles Jacobsen [this message]
2016-10-31 15:50 ` Mathieu Desnoyers
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=MWHPR11MB17756EC0046E84C041DF022398AD0@MWHPR11MB1775.namprd11.prod.outlook.com \
    --to=charles.jacobsen@primarydata.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