From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: [PATCH -v5][RFC]: mutex: implement adaptive spinning Date: Thu, 8 Jan 2009 15:45:41 +0100 Message-ID: <20090108144541.GA496@one.firstfloor.org> References: <1231365115.11687.361.camel@twins> <1231368870.6686.16.camel@norville.austin.ibm.com> <20090108065235.GX496@one.firstfloor.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Andi Kleen , Linus Torvalds , Dave Kleikamp , Peter Zijlstra , paulmck@linux.vnet.ibm.com, Gregory Haskins , Ingo Molnar , Matthew Wilcox , Chris Mason , Andrew Morton , Linux Kernel Mailing List , linux-fsdevel , linux-btrfs , Thomas Gleixner , Nick Piggin , Peter Morreale , Sven Dietrich To: Steven Rostedt Return-path: In-Reply-To: List-ID: > Sure, it probably is a non issue, but I'm afraid that non issues of today > might become issues of tomorrow. Where does it say that we can never put a > task struct in a movable zone. Task structs are not movable, so they by definition do not belong in movable zones. > memory local to it, and pinned tasks to that CPU in that memory. Then > there can be cases where we remove the CPU and memory together. If you did that you would need to redesign so much of the kernel, changing the mutex code too would be the smallest of your worries. -Andi -- ak@linux.intel.com