From: Andi Kleen <ak@muc.de>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: lhms <lhms-devel@lists.sourceforge.net>,
linux-mm <linux-mm@kvack.org>, Andy Whitcroft <apw@shadowen.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] Sparse Memory Handling (hot-add foundation)
Date: Fri, 18 Feb 2005 11:04:06 +0100 [thread overview]
Message-ID: <m1zmy2b2w9.fsf@muc.de> (raw)
In-Reply-To: <1108685033.6482.38.camel@localhost> (Dave Hansen's message of "Thu, 17 Feb 2005 16:03:53 -0800")
Dave Hansen <haveblue@us.ibm.com> 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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2005-02-18 10:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-18 0:03 Dave Hansen
2005-02-18 0:05 ` [RFC][PATCH] Memory Hotplug Dave Hansen
2005-02-18 21:52 ` Rik van Riel
2005-02-18 22:20 ` Dave Hansen
2005-02-19 1:48 ` Rik van Riel
2005-02-18 5:16 ` [RFC][PATCH] Sparse Memory Handling (hot-add foundation) Mike Kravetz
2005-02-18 15:31 ` Dave Hansen
2005-02-18 10:04 ` Andi Kleen [this message]
2005-02-18 15:42 ` Dave Hansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1zmy2b2w9.fsf@muc.de \
--to=ak@muc.de \
--cc=apw@shadowen.org \
--cc=haveblue@us.ibm.com \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox