From: rusty@rustcorp.com.au (Rusty Russell)
Subject: [lttng-dev] Coding blog: lockless queues
Date: Tue, 22 Jan 2013 09:29:49 +1030 [thread overview]
Message-ID: <87ip6quopm.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20130110165942.GA5133@Krystal>
Mathieu Desnoyers <mathieu.desnoyers at efficios.com> writes:
> Hi Rusty!
>
> I've stumbled on your blog post: http://rusty.ozlabs.org/?p=317
>
> and I find that you looked at the RCU lock-free queue implementation in
> the Userspace RCU project, but not at the wait-free concurrent queue
> implementation we have (wait-free enqueue, blocking dequeue), which does
> not require RCU at all and might be a much better fit for what you are
> trying to achieve.
Clearly, I stopped reading too early! It's a very nice
implementation...
If I revisit this, I'll do a code review and post it on my blog.
Thanks!
Rusty.
prev parent reply other threads:[~2013-01-21 22:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 16:59 Mathieu Desnoyers
2013-01-21 22:59 ` Rusty Russell [this message]
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=87ip6quopm.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
/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