From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: rp@svcs.cs.pdx.edu,
"Paul E . McKenney" <paulmck@linux.vnet.ibm.com>,
Stephen Hemminger <shemminger@vyatta.com>,
Alan Stern <stern@rowland.harvard.edu>,
jiangshanlai@gmail.com
Cc: lttng-dev@lists.lttng.org
Subject: [RFC PATCH liburcu 0/2] Remove RCU requirements on hash table destroy
Date: Tue, 30 May 2017 17:10:18 -0400 [thread overview]
Message-ID: <1496178620-14755-1-git-send-email-mathieu.desnoyers__370.899102608924$1496179100$gmane$org@efficios.com> (raw)
The RCU lock-free hash table currently requires that the destroy
function should not be called from within RCU read-side critical
sections. This is caused by the lazy resize, which uses the call_rcu
worker thread, even though all it really needs is a workqueue/worker
thread scheme.
Implement an internal workqueue API in liburcu, and use it instead of
call_rcu in rculfhash to overcome this limitation.
Mathieu Desnoyers (2):
Implement urcu workqueues internal API
Use workqueue in rculfhash
include/urcu/rculfhash.h | 15 +-
src/Makefile.am | 2 +-
src/rculfhash-internal.h | 2 +-
src/rculfhash.c | 124 ++++++------
src/workqueue.c | 507 +++++++++++++++++++++++++++++++++++++++++++++++
src/workqueue.h | 104 ++++++++++
6 files changed, 686 insertions(+), 68 deletions(-)
create mode 100644 src/workqueue.c
create mode 100644 src/workqueue.h
--
2.1.4
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next reply other threads:[~2017-05-30 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-30 21:10 Mathieu Desnoyers [this message]
[not found] <1496178620-14755-1-git-send-email-mathieu.desnoyers@efficios.com>
2017-06-05 22:56 ` [RFC PATCH liburcu 0/2] Remove RCU requirements on hash table destroy Paul E. McKenney
[not found] ` <20170605225608.GY3721@linux.vnet.ibm.com>
2017-06-06 18:07 ` 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='1496178620-14755-1-git-send-email-mathieu.desnoyers__370.899102608924$1496179100$gmane$org@efficios.com' \
--to=mathieu.desnoyers@efficios.com \
--cc=jiangshanlai@gmail.com \
--cc=lttng-dev@lists.lttng.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rp@svcs.cs.pdx.edu \
--cc=shemminger@vyatta.com \
--cc=stern@rowland.harvard.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.