[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20141112.154341.1705628294274955796.davem@davemloft.net>
Date: Wed, 12 Nov 2014 15:43:41 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: alexander.h.duyck@...hat.com
Cc: will.deacon@....com, alexander.duyck@...il.com,
linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org,
mikey@...ling.org, tony.luck@...el.com,
mathieu.desnoyers@...ymtl.ca, peterz@...radead.org,
benh@...nel.crashing.org, heiko.carstens@...ibm.com,
oleg@...hat.com, michael@...erman.id.au, geert@...ux-m68k.org,
fweisbec@...il.com, schwidefsky@...ibm.com, linux@....linux.org.uk,
paulmck@...ux.vnet.ibm.com, torvalds@...ux-foundation.org,
mingo@...nel.org
Subject: Re: [PATCH] arch: Introduce read_acquire()
From: Alexander Duyck <alexander.h.duyck@...hat.com>
Date: Tue, 11 Nov 2014 13:12:32 -0800
> The architectures I need to sort out are arm, x86, sparc, ia64, and
> s390 as they are the only ones that tried to make use of the
> smp_load_acquire logic.
On sparc64, you don't have to worry about anything really.
Only mb() does anything. The cpus execute in a reasonably strict
memory ordering mode, and that's why rmb/wmb and friends are simply
nops with a compiler barrier.
--
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