Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
* [lttng-dev] RCU on non-cache-coherent memory
@ 2016-08-02  0:30 Yuxin Ren
  2016-08-02 22:58 ` Mathieu Desnoyers
  0 siblings, 1 reply; 3+ messages in thread
From: Yuxin Ren @ 2016-08-02  0:30 UTC (permalink / raw)


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.

Thanks a lot!
Yuxin


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [lttng-dev] RCU on non-cache-coherent memory
  2016-08-02  0:30 [lttng-dev] RCU on non-cache-coherent memory Yuxin Ren
@ 2016-08-02 22:58 ` Mathieu Desnoyers
  2016-08-04 14:58   ` Paul E. McKenney
  0 siblings, 1 reply; 3+ messages in thread
From: Mathieu Desnoyers @ 2016-08-02 22:58 UTC (permalink / raw)


----- 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


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [lttng-dev] RCU on non-cache-coherent memory
  2016-08-02 22:58 ` Mathieu Desnoyers
@ 2016-08-04 14:58   ` Paul E. McKenney
  0 siblings, 0 replies; 3+ messages in thread
From: Paul E. McKenney @ 2016-08-04 14:58 UTC (permalink / raw)


On Tue, Aug 02, 2016 at 10:58:57PM +0000, Mathieu Desnoyers wrote:
> ----- 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.

Mathieu pretty much covered it.  We only have theoretical experience
with non-cache-coherent systems.  You might want to contact the authors
of these papers:

http://www.sigops.org/sosp/sosp11/posters/summaries/sosp11-final7.pdf
http://arxiv.org/pdf/1301.4490.pdf

There are probably others, as this was a hot topic a couple of years ago.

							Thanx, Paul



^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2016-08-04 14:58 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-08-02  0:30 [lttng-dev] RCU on non-cache-coherent memory Yuxin Ren
2016-08-02 22:58 ` Mathieu Desnoyers
2016-08-04 14:58   ` Paul E. McKenney

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox