Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760649AbZAHObs (ORCPT ); Thu, 8 Jan 2009 09:31:48 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758232AbZAHObi (ORCPT ); Thu, 8 Jan 2009 09:31:38 -0500 Received: from one.firstfloor.org ([213.235.205.2]:33694 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757003AbZAHObh (ORCPT ); Thu, 8 Jan 2009 09:31:37 -0500 Date: Thu, 8 Jan 2009 15:45:41 +0100 From: Andi Kleen To: Steven Rostedt 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 Subject: Re: [PATCH -v5][RFC]: mutex: implement adaptive spinning 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 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 822 Lines: 21 > 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 -- 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/