From mboxrd@z Thu Jan 1 00:00:00 1970 From: Johannes Weiner Subject: Re: [PATCH] mutex: set owner only once on acquisition Date: Thu, 15 Jan 2009 09:56:25 +0100 Message-ID: <20090115085625.GA15038@cmpxchg.org> References: <1231774622.4371.96.camel@laptop> <1231859742.442.128.camel@twins> <1231863710.7141.3.camel@twins> <1231864854.7141.8.camel@twins> <1231867314.7141.16.camel@twins> <20090115083951.GA13930@cmpxchg.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Linus Torvalds , Ingo Molnar , "Paul E. McKenney" , Gregory Haskins , Matthew Wilcox , Andi Kleen , Chris Mason , Andrew Morton , Linux Kernel Mailing List , linux-fsdevel , linux-btrfs , Thomas Gleixner , Nick Piggin , Peter Morreale , Sven Dietrich , Dmitry Adamushko To: Peter Zijlstra Return-path: Content-Disposition: inline In-Reply-To: <20090115083951.GA13930@cmpxchg.org> Sender: linux-btrfs-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Thu, Jan 15, 2009 at 09:41:01AM +0100, Johannes Weiner wrote: > mutex_lock() sets the lock owner, no need to set it upfront in > __mutex_lock_common(). > > Inside __mutex_lock_common() we can cope with the case where the > successful acquirer got preempted by us before setting the owner > field: there is an explicit check in the spinning code and the > sleeping part doesn't rely on it. > > The debug code does owner checks only on unlock where the field is > garuanteed to be set. > > Signed-off-by: Johannes Weiner > --- > kernel/mutex.c | 2 -- > 1 file changed, 2 deletions(-) > > Just a small observation. Peter said it wouldn't matter much as the > write is to a hot cache line. But otoh, why keep it if it's not > necessary. :) Damn, I'm really async here, sorry Peter. Just noticed you already picked it up. Hannes