[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <alpine.LFD.2.00.0809282114530.3635@xanadu.home>
Date: Sun, 28 Sep 2008 21:21:14 -0400 (EDT)
From: Nicolas Pitre <nico@....org>
To: Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc: David Howells <dhowells@...hat.com>, torvalds@...l.org,
akpm@...ux-foundation.org, linux-am33-list@...hat.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] MN10300: Move asm-arm/cnt32_to_63.h to include/linux/
On Fri, 26 Sep 2008, Peter Zijlstra wrote:
> On Fri, 2008-09-26 at 08:03 -0400, Nicolas Pitre wrote:
> > On Fri, 26 Sep 2008, Peter Zijlstra wrote:
> >
> > > On Wed, 2008-09-24 at 17:48 +0100, David Howells wrote:
> > > > Move asm-arm/cnt32_to_63.h to include/linux/ so that MN10300 can make use of it
> > > > too.
> > > >
> > > > Signed-off-by: David Howells <dhowells@...hat.com>
> > > > ---
> > > >
> > > > arch/arm/mach-pxa/time.c | 2 +
> > > > arch/arm/mach-sa1100/generic.c | 2 +
> > > > arch/arm/mach-versatile/core.c | 2 +
> > > > include/linux/cnt32_to_63.h | 80 ++++++++++++++++++++++++++++++++++++++++
> > > > 4 files changed, 83 insertions(+), 3 deletions(-)
> > > > create mode 100644 include/linux/cnt32_to_63.h
> > >
> > > Didn't you forget to remove the old one?
> > >
> > >
> > > > +#define cnt32_to_63(cnt_lo) \
> > > > +({ \
> > > > + static volatile u32 __m_cnt_hi; \
> > > > + union cnt32_to_63 __x; \
> > > > + __x.hi = __m_cnt_hi; \
> > > > + __x.lo = (cnt_lo); \
> > > > + if (unlikely((s32)(__x.hi ^ __x.lo) < 0)) \
> > > > + __m_cnt_hi = __x.hi = (__x.hi ^ 0x80000000) + (__x.hi >> 31); \
> > > > + __x.val; \
> > > > +})
> > > > +
> > > > +#endif
> > >
> > > That code is way to smart :-)
> > >
> > > Better make sure that non of its users are SMP capable though.
> >
> > Why would that matter?
>
> It has a local static variable and no synchronization.
So? The whole point of this algorithm is to avoid all kind of locking
and require absolutely no synchronization as it relies solely on the
implicit synchronization from the top bit of both values. You would get
cache bouncing but the result will still be correct.
> Also, if the counters differ per cpu the value of __m_cnt_hi ought to
> be different per cpu.
True.
Nicolas
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists