From: lolkaantimat@gmail.com (Evgeniy Ivanov)
Subject: [lttng-dev] Userspace RCU VS spin locks
Date: Fri, 1 Nov 2013 12:13:06 +0400 [thread overview]
Message-ID: <CAO6Ho0eDS-RrOUN1jM3zYL9fvmrqf1uAkF4kpCaE+dYSX_Ufxg@mail.gmail.com> (raw)
In-Reply-To: <990689914.54025.1383219361284.JavaMail.zimbra@efficios.com>
Thanks a lot, Mathieu!
On Thu, Oct 31, 2013 at 3:36 PM, Mathieu Desnoyers
<mathieu.desnoyers at efficios.com> wrote:
> ----- Original Message -----
>> From: "Evgeniy Ivanov" <lolkaantimat@gmail.com>
>> To: lttng-dev at lists.lttng.org
>> Sent: Wednesday, October 30, 2013 9:11:47 AM
>> Subject: [lttng-dev] Userspace RCU VS spin locks
>>
>> Hi,
>>
>> I'm very interested in RCU performance, especially applied to hash
>> tables (rculfhash in particular). Did any body compare performance of
>> QSBR or signal RCU VS scalable and non-scalable spin locks?
>>
>
> Hi Evgeniy,
>
> You'll probably want to start by looking at my Linux Plumbers slides presenting rculfhash:
>
> https://www.efficios.com/lpc2011-urcu
>
> Also, Paul McKenney's slides of the Userspace RCU tutorial here present other numbers of a hash table example (including bucket-locks), AFAIK using his own statically sized hash table implementation (not rculfhash):
>
> https://events.linuxfoundation.org/sites/events/files/slides/userspace-rcu-tutorial-linuxcon-2013.pdf
>
> Thanks,
>
> Mathieu
>
>
>
>> --
>> Cheers,
>> Evgeniy
>>
>> _______________________________________________
>> lttng-dev mailing list
>> lttng-dev at lists.lttng.org
>> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>>
>
> --
> Mathieu Desnoyers
> EfficiOS Inc.
> http://www.efficios.com
--
Cheers,
Evgeniy
parent reply other threads:[~2013-11-01 8:13 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <990689914.54025.1383219361284.JavaMail.zimbra@efficios.com>]
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=CAO6Ho0eDS-RrOUN1jM3zYL9fvmrqf1uAkF4kpCaE+dYSX_Ufxg@mail.gmail.com \
--to=lolkaantimat@gmail.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