Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [lttng-dev] RCU on non-cache-coherent memory
Date: Tue, 2 Aug 2016 22:58:57 +0000 (UTC)	[thread overview]
Message-ID: <1648244903.1131.1470178737812.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <CAAKbDrfJ=umcdwFp7j5RDMZt7AfhAhCnmOfZqvD2WeNuhcb0rw@mail.gmail.com>

----- On Aug 1, 2016, at 8:30 PM, Yuxin Ren ryx at gwmail.gwu.edu wrote:

> Hi all,
> 
> Is there any research or publications about RCU on top of
> non-cache-coherent multi-core architecture?
> Not only RCU, any other synchronization technique on top of
> non-cache-coherent multi-core
> is also helpful.

CCing Paul E. McKenney, who might know more on this topic.

Back in 2009 when I started the liburcu.org project, I
planned to eventually add support for such architectures,
e.g. Blackfin, which is why I initially added the cmm_mc(),
cmm_rmc() and cmm_wmc() macros in the library (see
CONFIG_HAVE_MEM_COHERENCY). However, all currently implemented
architectures have mem coherency, so it's always defined as a
simple compiler barrier. See include/urcu/arch/generic.h in liburcu
for details.

Thanks,

Mathieu

> 
> Thanks a lot!
> Yuxin
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com


  reply	other threads:[~2016-08-02 22:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-02  0:30 Yuxin Ren
2016-08-02 22:58 ` Mathieu Desnoyers [this message]
2016-08-04 14:58   ` Paul E. McKenney

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=1648244903.1131.1470178737812.JavaMail.zimbra@efficios.com \
    --to=mathieu.desnoyers@efficios.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