Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 28 Aug 2002 17:35:40 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 28 Aug 2002 17:35:40 -0400 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:33293 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id ; Wed, 28 Aug 2002 17:35:40 -0400 To: linux-kernel@vger.kernel.org From: "H. Peter Anvin" Subject: Re: atomic64_t proposal Date: 28 Aug 2002 14:39:28 -0700 Organization: Transmeta Corporation, Santa Clara CA Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Disclaimer: Not speaking for Transmeta in any way, shape, or form. Copyright: Copyright 2002 H. Peter Anvin - All Rights Reserved Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1008 Lines: 23 Followup to: By author: Robin Holt In newsgroup: linux.dev.kernel > > I do like the atomic_inc, atomic_dec, etc being able to handle either > type. While producing code, I can do a simple check at the beginning of > the block and define the appropriate type for a particular architecture. > Great. How do you expect to implement atomic_inc() et al so that that can actually be done? Consider that atomic64_t may very well need full-blown spinlocks, whereas a 32-bit atomic_t may not. -hpa -- at work, in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt - 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/