linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: mgross@linux.intel.com
Cc: pbadari@gmail.com, linux-mm@kvack.org, y-goto@jp.fujitsu.com
Subject: Re: Hotplug memory remove
Date: Sat, 6 Oct 2007 09:41:15 +0900	[thread overview]
Message-ID: <20071006094115.8b488e55.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20071005172128.GA19681@linux.intel.com>

On Fri, 5 Oct 2007 10:21:28 -0700
Mark Gross <mgross@linux.intel.com> wrote:

> > I'm not sure about this...does this memory is in ZONE_MOVABLE ?
> > If not ZONE_MOVABLE, offlining can be fail because of not-removable
> > kernel memory. 
> 
> How could I mark a nid's worth of memory as ZONE_MOVABLE?  I've been
> reading through this code and it appears to somewhat arbitrarily choose
> some portion of the memory to be ZONE_MOVABLE per pxm and some kernel
> parameters.  But I'm having a hard time finding the proper place to set
> up the nodes.
> 
It's not available now.

One idea is to ignore memory of some PXMs specified by kerenel boot param.
Later, you can hot-add specified PXM memory as MOVABLE.
Then, boot sequence will be
--
   bootstrap , ignore some memory here.
   init memory, driver, etc
   hot-add ignored memory
   online hot-added memory by user scripts. (from rc script ?)
--
For doing this, we need
 - a switch to hot-add memory as MOVABLE (will be easy patch)
 - a code for ignoring memory at boot but remember them for later hotadd
   (maybe needs arch specific codes)
 - a code for hot add memory before rc script (initcall is suitable ?) 

Needs some amount of arch-specific codes, but maybe simple.
Why I recommend above is it will be complex to avoid some PXM's memory
to be used as bootmem or for some other purpose(slab, hash, etc...).

If your firmware (efi?) doesn't show memory for hot removal at boot time,
this idea will be simpler..


Thanks,
-Kame

--
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:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2007-10-06  0:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-01 15:37 Badari Pulavarty
2007-10-01 16:14 ` KAMEZAWA Hiroyuki
2007-10-01 17:49   ` Badari Pulavarty
2007-10-02  0:52     ` KAMEZAWA Hiroyuki
2007-10-02 14:58       ` Badari Pulavarty
2007-10-02 17:17       ` Badari Pulavarty
2007-10-03  1:07         ` KAMEZAWA Hiroyuki
2007-10-05 17:21   ` Mark Gross
2007-10-06  0:41     ` KAMEZAWA Hiroyuki [this message]
2007-10-08 19:01       ` Mark Gross
2007-10-09  1:10         ` KAMEZAWA Hiroyuki
2007-10-09 10:51           ` 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=20071006094115.8b488e55.kamezawa.hiroyu@jp.fujitsu.com \
    --to=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=mgross@linux.intel.com \
    --cc=pbadari@gmail.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