Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752254AbaANXo4 (ORCPT ); Tue, 14 Jan 2014 18:44:56 -0500 Received: from e32.co.us.ibm.com ([32.97.110.150]:39452 "EHLO e32.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750918AbaANXos (ORCPT ); Tue, 14 Jan 2014 18:44:48 -0500 Date: Tue, 14 Jan 2014 15:44:43 -0800 From: "Paul E. McKenney" To: Richard Henderson Cc: Matt Turner , Peter Zijlstra , Daniel J Blueman , Waiman Long , Linux Kernel , Ivan Kokshaysky , Linus Torvalds Subject: Re: [PATCH v8 4/4] qrwlock: Use smp_store_release() in write_unlock() Message-ID: <20140114234443.GY10038@linux.vnet.ibm.com> Reply-To: paulmck@linux.vnet.ibm.com References: <52D353C8.4000000@numascale.com> <52D4172E.6030706@hp.com> <52D4A0C7.5070601@numascale.com> <20140114110307.GW7572@laptop.programming.kicks-ass.net> <52D57B60.9020209@twiddle.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <52D57B60.9020209@twiddle.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 14011423-0928-0000-0000-000005A2E581 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 14, 2014 at 10:01:04AM -0800, Richard Henderson wrote: > On 01/14/2014 09:08 AM, Matt Turner wrote: > > On Tue, Jan 14, 2014 at 3:03 AM, Peter Zijlstra wrote: > >> On Tue, Jan 14, 2014 at 10:28:23AM +0800, Daniel J Blueman wrote: > >>>> Peter, > >>>> > >>>> I found out that the build failure was caused by the fact that the > >>>> __native_word() macro (used internally by compiletime_assert_atomic()) > >>>> allows only a size of 4 or 8 for x86-64. The data type that I used is a > >>>> byte. Is there a reason why byte and short are not considered native? > >>> > >>> It seems likely it was implemented like that since there was no existing > >>> need; long can be relied on as the largest native type, so this should > >>> suffice and works here: > >> > >> There's Alphas that cannot actually atomically adres a byte; I do not > >> konw if Linux cares about them, but if it does, we cannot in fact rely > >> on this in generic primitives like this. > > > > That's right, and thanks for the heads-up. Alpha can only address 4 > > and 8 bytes atomically. (LDL_L, LDQ_L, STL_C, STQ_C). > > > > The Byte-Word extension in EV56 doesn't add new atomics, so in fact no > > Alphas can address < 4 bytes atomically. > > Emulated with aligned 4 byte atomics, and masking. The same is true for arm, > ppc, mips which, depending on cpu, also lack < 4 byte atomics. Which means that Alpha should be able to similarly emulate 1-byte and 2-byte atomics, correct? Thanx, Paul -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/