From: Matt Bucknall <matt@mattbucknall.com>
To: alsa-devel@alsa-project.org
Subject: Lock free ring buffers and SMP safety
Date: Sun, 18 Nov 2007 17:31:52 +0000 [thread overview]
Message-ID: <47407708.2080902@mattbucknall.com> (raw)
Hello,
Yes, this old chestnut. I've spent the best part of today trying to
ascertain whether or not, in practical terms, a single-producer,
single-consumer lock free ring-buffer can be written purely in C/C++ and
be SMP safe on multiple architectures without memory barriers.
Information I've found has been largely conflicting so I've given up
trying to get a conclusive answer. Instead I'll just go with the flow.
What is the general consensus amongst ALSA application developers when
it comes to implementing this kind of buffer? Is it possible to use
memory barriers through some user space API call that I don't know about?
Thanks in advance for any comments/suggestions.
Matt.
next reply other threads:[~2007-11-18 17:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-18 17:31 Matt Bucknall [this message]
2007-11-23 17:15 ` Lock free ring buffers and SMP safety Takashi Iwai
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=47407708.2080902@mattbucknall.com \
--to=matt@mattbucknall.com \
--cc=alsa-devel@alsa-project.org \
/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.