[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <f95b4ab810e3850f92ee7e98a1219bb2@kernel.crashing.org>
Date: Tue, 21 Aug 2007 00:07:15 +0200
From: Segher Boessenkool <segher@...nel.crashing.org>
To: Chris Snook <csnook@...hat.com>
Cc: Christoph Lameter <clameter@....com>,
Paul Mackerras <paulus@...ba.org>, heiko.carstens@...ibm.com,
Stefan Richter <stefanr@...6.in-berlin.de>, horms@...ge.net.au,
Satyam Sharma <satyam@...radead.org>,
Ilpo Jarvinen <ilpo.jarvinen@...sinki.fi>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
David Miller <davem@...emloft.net>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>, ak@...e.de,
Netdev <netdev@...r.kernel.org>, cfriesen@...tel.com,
rpjday@...dspring.com, jesper.juhl@...il.com,
linux-arch@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>, zlynx@....org,
schwidefsky@...ibm.com, Herbert Xu <herbert.xu@...hat.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
wensong@...ux-vs.org, Nick Piggin <piggin@...erone.com.au>,
wjiang@...ilience.com
Subject: Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures
> Such code generally doesn't care precisely when it gets the update,
> just that the update is atomic, and it doesn't loop forever.
Yes, it _does_ care that it gets the update _at all_, and preferably
as early as possible.
> Regardless, I'm convinced we just need to do it all in assembly.
So do you want "volatile asm" or "plain asm", for atomic_read()?
The asm version has two ways to go about it too...
Segher
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists