From: Andi Kleen <ak@suse.de>
To: Keith Mannthey <kmannth@gmail.com>
Cc: Andi Kleen <ak@muc.de>, 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: [discuss] Re: [patch 3/3] add x86-64 support for memory hot-add
Date: Sat, 10 Dec 2005 04:26:44 +0100 [thread overview]
Message-ID: <20051210032644.GJ15804@wotan.suse.de> (raw)
In-Reply-To: <a762e240512091616l62f1c69andeec382d7356ba64@mail.gmail.com>
On Fri, Dec 09, 2005 at 04:16:41PM -0800, Keith Mannthey wrote:
> > 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?
It's 2MB pages in 3levels, so roughly 3*8=24 bytes per 2MB or roughly
512 bytes per GB (rounded up always to the next page)
>
> > (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.
You're just proving someone's (anyone want to volunteer their name? ;-]
I think Linus pointed it out originally, so let's call it Linus')
law - as soon as we use some BIOS feature we soon find a BIOS
that will get it totally wrong.
Anyways, I retracted anyways because of some other issues so Matt's
original approach should be ok.
-Andi
prev parent reply other threads:[~2005-12-10 3:26 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 ` [patch 3/3] add x86-64 support for memory hot-add Keith Mannthey
2005-12-10 3:26 ` Andi Kleen [this message]
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=20051210032644.GJ15804@wotan.suse.de \
--to=ak@suse.de \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=discuss@x86-64.org \
--cc=kmannth@gmail.com \
--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
Powered by JetHome