Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753030AbWLWJhx (ORCPT ); Sat, 23 Dec 2006 04:37:53 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753098AbWLWJhw (ORCPT ); Sat, 23 Dec 2006 04:37:52 -0500 Received: from gprs189-60.eurotel.cz ([160.218.189.60]:1182 "EHLO spitz.ucw.cz" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753030AbWLWJhb (ORCPT ); Sat, 23 Dec 2006 04:37:31 -0500 Date: Sat, 23 Dec 2006 09:33:58 +0000 From: Pavel Machek To: Mathieu Desnoyers Cc: linux-kernel@vger.kernel.org, Andrew Morton , Ingo Molnar , Greg Kroah-Hartman , Christoph Hellwig , ltt-dev@shafik.org, systemtap@sources.redhat.com, Douglas Niehaus , "Martin J. Bligh" , Thomas Gleixner Subject: Re: [PATCH 0/10] local_t : adding and standardising atomic primitives Message-ID: <20061223093358.GF3960@ucw.cz> References: <20061221001545.GP28643@Krystal> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061221001545.GP28643@Krystal> User-Agent: Mutt/1.5.9i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 795 Lines: 19 Hi! > These patches extend and standardise local_t operations on each architectures, > allowing a rich set of atomic operations to be done on per-cpu data with > minimal performance impact. On some architectures, there seems to be no > difference between the SMP and UP operation (same memory barriers, same > LOCking), local.h simply includes asm-generic/local.h, which removes duplicated > code. Could you provide some Documentation/? Knowing when local_t can be used is kind-of important. Pavel -- Thanks for all the (sleeping) penguins. - 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/