From: Mark Gross <mgross@linux.intel.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Badari Pulavarty <pbadari@gmail.com>, linux-mm@kvack.org
Subject: Re: Hotplug memory remove
Date: Fri, 5 Oct 2007 10:21:28 -0700 [thread overview]
Message-ID: <20071005172128.GA19681@linux.intel.com> (raw)
In-Reply-To: <20071002011447.7ec1f513.kamezawa.hiroyu@jp.fujitsu.com>
On Tue, Oct 02, 2007 at 01:14:47AM +0900, KAMEZAWA Hiroyuki wrote:
> On Mon, 01 Oct 2007 08:37:43 -0700
> Badari Pulavarty <pbadari@gmail.com> wrote:
> > 1) Other than remove_memory(), I don't see any other arch-specific
> > code that needs to be provided. Even remove_memory() looks pretty
> > arch independent. Isn't it ?
> >
> Yes, maybe arch independent. Current codes is based on assumption
> that some arch may needs some code before/after hotremove.
> If no arch needs, we can merge all.
>
> > 2) I copied remove_memory() from IA64 to PPC64. When I am testing
> > hotplug-remove (echo offline > state), I am not able to remove
> > any memory at all. I get different type of failures like ..
> >
> > memory offlining 6e000 to 6f000 failed
> >
> 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.
btw: I'm trying to finish up that power managed memory experiment where we
set up numa PXM's marking fbdims we want to fiddle with power state on.
--mgross
--
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>
next prev parent reply other threads:[~2007-10-05 17:21 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 [this message]
2007-10-06 0:41 ` KAMEZAWA Hiroyuki
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=20071005172128.GA19681@linux.intel.com \
--to=mgross@linux.intel.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=pbadari@gmail.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