Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932526AbVLNC5M (ORCPT ); Tue, 13 Dec 2005 21:57:12 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932603AbVLNC5M (ORCPT ); Tue, 13 Dec 2005 21:57:12 -0500 Received: from cantor2.suse.de ([195.135.220.15]:52154 "EHLO mx2.suse.de") by vger.kernel.org with ESMTP id S932526AbVLNC5M (ORCPT ); Tue, 13 Dec 2005 21:57:12 -0500 Date: Wed, 14 Dec 2005 03:57:10 +0100 From: Andi Kleen To: Christoph Lameter Cc: Andrew Morton , linux-kernel@vger.kernel.org, ak@suse.de Subject: Re: [PATCH] atomic_long_t & include/asm-generic/atomic.h V2 Message-ID: <20051214025710.GD23384@wotan.suse.de> References: <20051213154916.6667b6d8.akpm@osdl.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 756 Lines: 18 > > How about requiring that all 64-bit archs implement atomic64_t and do: > > It may be reasonable to have 64 bit arches that are not > capable of 64 bit atomic ops. As far as I can remember sparc was initially > a 32 bit platform without 32 bit atomic ops. Why? I don't think we have any crippled 64bit platforms like this. And if somebody wants to port linux to such a hypothetical crippled 64bit platform they can do the necessary work themselves. Or just implement 64bit atomic_t with spinlocks. -Andi - 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/