Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261328AbVBRKEL (ORCPT ); Fri, 18 Feb 2005 05:04:11 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261326AbVBRKEL (ORCPT ); Fri, 18 Feb 2005 05:04:11 -0500 Received: from one.firstfloor.org ([213.235.205.2]:12942 "EHLO one.firstfloor.org") by vger.kernel.org with ESMTP id S261169AbVBRKEJ (ORCPT ); Fri, 18 Feb 2005 05:04:09 -0500 To: Dave Hansen Cc: lhms , linux-mm , Andy Whitcroft , linux-kernel@vger.kernel.org Subject: Re: [RFC][PATCH] Sparse Memory Handling (hot-add foundation) References: <1108685033.6482.38.camel@localhost> From: Andi Kleen Date: Fri, 18 Feb 2005 11:04:06 +0100 In-Reply-To: <1108685033.6482.38.camel@localhost> (Dave Hansen's message of "Thu, 17 Feb 2005 16:03:53 -0800") Message-ID: User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 889 Lines: 21 Dave Hansen writes: > The attached patch, largely written by Andy Whitcroft, implements a > feature which is similar to DISCONTIGMEM, but has some added features. > Instead of splitting up the mem_map for each NUMA node, this splits it > up into areas that represent fixed blocks of memory. This allows > individual pieces of that memory to be easily added and removed. [...] I'm curious - how does this affect .text size for a i386 or x86-64 NUMA kernel? One area I wanted to improve on x86-64 for a long time was to shrink the big virt_to_page() etc. inline macros. Your new code actually looks a bit smaller. -Andi - 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/