Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S268323AbUIPXV7 (ORCPT ); Thu, 16 Sep 2004 19:21:59 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S268435AbUIPXUd (ORCPT ); Thu, 16 Sep 2004 19:20:33 -0400 Received: from dragnfire.mtl.istop.com ([66.11.160.179]:37581 "EHLO dsl.commfireservices.com") by vger.kernel.org with ESMTP id S268337AbUIPXUL (ORCPT ); Thu, 16 Sep 2004 19:20:11 -0400 Date: Thu, 16 Sep 2004 19:20:09 +0000 (UTC) From: Zwane Mwaikambo To: Ray Bryant Cc: Ray Bryant , Andrew Morton , lse-tech@lists.sourceforge.net, "Martin J. Bligh" , linux-kernel@vger.kernel.org Subject: Re: [PATCH 2/3] lockmeter: lockmeter fix for generic_read_trylock In-Reply-To: <20040916230402.23023.89478.83475@tomahawk.engr.sgi.com> Message-ID: References: <20040916230344.23023.79384.49263@tomahawk.engr.sgi.com> <20040916230402.23023.89478.83475@tomahawk.engr.sgi.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 707 Lines: 24 On Thu, 16 Sep 2004, Ray Bryant wrote: > Update lockmeter.c with generic_raw_read_trylock fix. > > + * Generic declaration of the raw read_trylock() function, > + * architectures are supposed to optimize this: > + */ > +int __lockfunc generic_raw_read_trylock(rwlock_t *lock) > +{ > + _metered_read_lock(lock, __builtin_return_address(0)); > + return 1; > +} What's really going on here? I'm slightly confused by the _metered_read_lock usage. Thanks, Zwane - 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/