From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Subject: Re: [PATCH -v5][RFC]: mutex: implement adaptive spinning Date: Wed, 7 Jan 2009 23:33:17 +0100 Message-ID: <20090107223317.GB27629@elte.hu> References: <1231283778.11687.136.camel@twins> <1231329783.11687.287.camel@twins> <1231347442.11687.344.camel@twins> <20090107210923.GV2002@parisc-linux.org> <20090107213924.GP496@one.firstfloor.org> <49652C7C.3000909@novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Andi Kleen , Matthew Wilcox , Linus Torvalds , Steven Rostedt , Peter Zijlstra , paulmck@linux.vnet.ibm.com, Chris Mason , Andrew Morton , Linux Kernel Mailing List , linux-fsdevel , linux-btrfs , Thomas Gleixner , Nick Piggin , Peter Morreale , Sven Dietrich To: Gregory Haskins Return-path: In-Reply-To: <49652C7C.3000909@novell.com> List-ID: * Gregory Haskins wrote: > Can I ask a simple question in light of all this discussion? > > "Is get_task_struct() really that bad?" it dirties a cacheline and it also involves atomics. Also, it's a small design cleanliness issue to me: get_task_struct() impacts the lifetime of an object - and if a locking primitive has side-effects on object lifetimes that's never nice. Ingo