* Mathieu Desnoyers <mathieu.desnoy...@efficios.com> wrote:
> > it's offline right now:
> >
> > $ git clone git://git.lttng.org/urcu
> > Cloning into urcu...
> > fatal: The remote end hung up unexpectedly
>
> This would be:
>
> git clone git://git.lttng.org/userspace-rcu.git
Hey, my impression wasn't *entirely* wrong, your initial urcu commit:
From 27b012e271a82b9a0d94543688904f207cd154ea Mon Sep 17 00:00:00 2001
From: Mathieu Desnoyers <mathieu.desnoy...@polymtl.ca>
Date: Thu, 5 Feb 2009 19:06:44 -0500
Subject: [PATCH] init version
---
Makefile | 6 ++
urcu.c | 250 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
urcu.h | 69 +++++++++++++++++
3 files changed, 325 insertions(+), 0 deletions(-)
Has:
+/* The "volatile" is due to gcc bugs */
+#define barrier() __asm__ __volatile__("": : :"memory")
+
Which code sequence i recognize very well as a kernel maintainer ;-)
Here's the kernel's compiler.h definition of the same:
/* The "volatile" is due to gcc bugs */
#define barrier() __asm__ __volatile__("": : :"memory")
This:
+/* x86 32/64 specific */
+#define mb() asm volatile("mfence":::"memory")
+#define rmb() asm volatile("lfence":::"memory")
+#define wmb() asm volatile("sfence" ::: "memory")
+
+
+
+/* x86 32 */
+static inline void atomic_inc(int *v)
+{
+ asm volatile("lock; incl %0"
+ : "+m" (v->counter));
is familiar to an arch/x86/ maintainer as well :-)
So yes, kernel code was obviously used in the making of urcu - just
not the RCU kernel code it appears.
Which is a pity i think! :-)
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
