mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Keith Mannthey <kmannth@gmail.com>
To: Andi Kleen <ak@muc.de>
Cc: Matt Tolentino <metolent@cs.vt.edu>,
	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: Fri, 9 Dec 2005 16:16:41 -0800	[thread overview]
Message-ID: <a762e240512091616l62f1c69andeec382d7356ba64@mail.gmail.com> (raw)
In-Reply-To: <20051209173249.GA54033@muc.de>

> 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.

How much overhead would there be?

> (i.e. instead of extending the kernel mapping preallocate
> the direct mapping and just clear the P bits)

On my box the SRAT for hot-add areas exposed are from the end
installed memory to way out in outerspace.
SRAT: hot plug zone found 280000000 - 2300000000
I can't hot add that sort of range on my box but the bios didn't want
to limit or is planing for really really big dimms.

I wouldn't want to waste resource for areas that will never be added.

Thanks,
 Keith

  parent reply	other threads:[~2005-12-10  0:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-09 15:23 Matt Tolentino
2005-12-09 17:32 ` Andi Kleen
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   ` Keith Mannthey [this message]
2005-12-10  3:26     ` [discuss] Re: [patch 3/3] add x86-64 support for memory hot-add 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=a762e240512091616l62f1c69andeec382d7356ba64@mail.gmail.com \
    --to=kmannth@gmail.com \
    --cc=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
all inboxes | Powered by JetHome®