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 07:52:35 +0100 Message-ID: <20090108065235.GX496@one.firstfloor.org> References: <1231347442.11687.344.camel@twins> <1231365115.11687.361.camel@twins> <1231368870.6686.16.camel@norville.austin.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Linus Torvalds , Dave Kleikamp , Peter Zijlstra , paulmck@linux.vnet.ibm.com, Gregory Haskins , Ingo Molnar , Matthew Wilcox , Andi Kleen , 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: Received: from one.firstfloor.org ([213.235.205.2]:45716 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751710AbZAHGid (ORCPT ); Thu, 8 Jan 2009 01:38:33 -0500 Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: > What about memory hotplug as Ingo mentioned? > > Should that be: > > #if defined(CONFIG_DEBUG_PAGEALLOC) || defined(CONFIG_MEMORY_HOTPLUG) We expect memory hotunplug to only really work in movable zones (all others should at least have one kernel object somewhere that prevents unplug) and you can't have task structs in movable zones obviously So it's probably a non issue in practice. -Andi -- ak@linux.intel.com