From: Andi Kleen <ak@muc.de>
To: Matt Tolentino <metolent@cs.vt.edu>
Cc: akpm@osdl.org, discuss@x86-64.org, linux-kernel@vger.kernel.org,
matthew.e.tolentino@intel.com
Subject: Re: [patch 3/3] add x86-64 support for memory hot-add
Date: 9 Dec 2005 18:32:49 +0100
Date: Fri, 9 Dec 2005 18:32:49 +0100 [thread overview]
Message-ID: <20051209173249.GA54033@muc.de> (raw)
In-Reply-To: <200512091523.jB9FNn5J006697@ap1.cs.vt.edu>
On Fri, Dec 09, 2005 at 10:23:49AM -0500, Matt Tolentino wrote:
> --- linux-2.6.15-rc5/arch/x86_64/mm/init.c 2005-12-04 00:10:42.000000000 -0500
> +++ linux-2.6.15-rc5-matt/arch/x86_64/mm/init.c 2005-12-08 15:02:30.000000000 -0500
> @@ -23,6 +23,8 @@
> #include <linux/bootmem.h>
> #include <linux/proc_fs.h>
> #include <linux/pci.h>
> +#include <linux/module.h>
> +#include <linux/memory_hotplug.h>
>
> #include <asm/processor.h>
> #include <asm/system.h>
> @@ -174,13 +176,19 @@ static struct temp_map {
> {}
> };
>
> -static __init void *alloc_low_page(int *index, unsigned long *phys)
> +static __devinit void *alloc_low_page(int *index, unsigned long *phys)
These should be all __cpuinit.
In general SRAT has a hotplug memory bit so it's possible
to predict how much memory there will be in advance. Since
the overhead of the kernel page tables should be very
low I would prefer if you just used instead.
(i.e. instead of extending the kernel mapping preallocate
the direct mapping and just clear the P bits)
That should be much simpler.
-Andi
next prev parent reply other threads:[~2005-12-09 17:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-09 15:23 [patch 3/3] add x86-64 support for memory hot-add Matt Tolentino
2005-12-09 17:32 ` Andi Kleen [this message]
2005-12-09 17:49 ` [discuss] Re: [patch 3/3] add x86-64 support for memory hot-add II Andi Kleen
2005-12-10 0:16 ` [patch 3/3] add x86-64 support for memory hot-add Keith Mannthey
2005-12-10 3:26 ` [discuss] " Andi Kleen
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=20051209173249.GA54033@muc.de \
--to=ak@muc.de \
--cc=akpm@osdl.org \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.e.tolentino@intel.com \
--cc=metolent@cs.vt.edu \
/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