public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Geoff Levand <geoffrey.levand@am.sony.com>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: Milton Miller <miltonm@bga.com>,
	Christoph Lameter <clameter@sgi.com>,
	Andy Whitcroft <apw@shadowen.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Yasunori Goto <y-goto@jp.fujitsu.com>
Subject: Re: PS3: trouble with SPARSEMEM_VMEMMAP and kexec
Date: Tue, 04 Dec 2007 20:56:09 -0800	[thread overview]
Message-ID: <47562F69.7010508@am.sony.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0712040925470.16793@pademelon.sonytel.be>

Geert Uytterhoeven wrote:
> On Mon, 3 Dec 2007, Milton Miller wrote:
>> Chris, as you can see, PS3 needs to allocate 1/8th of total initial memory to
>> add any more memory.  Geoff, can you predict what linear address the
>> additional memory will occupy?  Judging from the attempted address toa add,
>> maybe not.   If not, my only thought is to pre-reserve an additional page and
>> consume it on the first add.   Additional adds will likely draw from the first
>> added region, pinning.
> 
> To me it sounds a bit strange that hotplug memory relies on having huge
> contiguous blocks of memory available. If this isn't done very early in the
> boot process, changes are high it will fail.
> 
> Would it be possible to allocate the memory from the newly added block, which
> is guaranteed to be unfragmented?


Yes, this sounds like a cleaner solution than pre-allocating, as the memory is
there and its properties are known.

-Geoff



  reply	other threads:[~2007-12-05  4:56 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-03  3:59 PS3: trouble with SPARSEMEM_VMEMMAP and kexec Geoff Levand
2007-12-03 15:53 ` Milton Miller
2007-12-04  8:30   ` Geert Uytterhoeven
2007-12-05  4:56     ` Geoff Levand [this message]
2007-12-05  4:55   ` Geoff Levand
2007-12-05  9:52   ` Geert Uytterhoeven
2007-12-05 23:11     ` Andrew Morton
2007-12-05 23:45       ` Geoff Levand
2007-12-06  6:09         ` Yasunori Goto
2007-12-06  9:55           ` Geert Uytterhoeven
2007-12-06  9:55             ` Geert Uytterhoeven
2007-12-06 10:48               ` Yasunori Goto
2007-12-08  2:47                 ` Geoff Levand
2007-12-10  1:55                   ` Yasunori Goto
2007-12-08  3:26           ` Geoff Levand
2007-12-08  3:49             ` oops with 2.6.23.1, marvel, software raid, reiserfs and samba jeffunit
2007-12-16 11:05               ` Andrew Morton
2007-12-16 11:56                 ` Herbert Xu
2007-12-16 12:21                   ` Herbert Xu
2007-12-16 14:55                 ` jeffunit
2007-12-16 22:09                   ` Andrew Morton
2007-12-06  7:41         ` PS3: trouble with SPARSEMEM_VMEMMAP and kexec Geert Uytterhoeven
2007-12-07  5:55           ` Geoff Levand
2007-12-06  5:44       ` Geoff Levand
2007-12-09  4:22 ` sparsemem: Make SPARSEMEM_VMEMMAP selectable Geoff Levand
2007-12-10  5:50   ` Yasunori Goto

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=47562F69.7010508@am.sony.com \
    --to=geoffrey.levand@am.sony.com \
    --cc=Geert.Uytterhoeven@sonycom.com \
    --cc=apw@shadowen.org \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miltonm@bga.com \
    --cc=y-goto@jp.fujitsu.com \
    /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