From: Yasunori Goto <y-goto@jp.fujitsu.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Andi Kleen <ak@suse.de>, "Brown, Len" <len.brown@intel.com>,
"Tolentino, Matthew E" <matthew.e.tolentino@intel.com>,
"S, Naveen B" <naveen.b.s@intel.com>,
Bjorn Helgaas <bjorn.helgaas@hp.com>,
ACPI-ML <linux-acpi@vger.kernel.org>,
Linux Kernel ML <linux-kernel@vger.kernel.org>,
linux-ia64@vger.kernel.org, x86-64 Discuss <discuss@x86-64.org>,
Linux Hotplug Memory Support <lhms-devel@lists.sourceforge.net>
Subject: Re: [Lhms-devel] [RFC:PATCH(000/003)] Memory add to onlined node. (ver. 2)
Date: Fri, 10 Feb 2006 01:49:06 +0000 [thread overview]
Message-ID: <20060210103730.AFC7.Y-GOTO@jp.fujitsu.com> (raw)
In-Reply-To: <B8E391BBE9FE384DAA4C5C003888BE6F05AA16C3@scsmsx401.amr.corp.intel.com>
> > - if the node is already online.- If the node is offline,
> > (It means new node is comming!) then the memory will belongs
> > to node 0 yet.
>
> What is the long term plan to address this? Can you make sure
> that the new node is always brought online before you get to
> this code? Or will you have to bring the node online in the
> middle of the memory hot-add code?
I still have patches for new pgdat addtion,
But I was afraid that everyone think they are messy due to too much code.
So, I tried to post a part of them step by step.
Ok, I would like to try to rebase and repost them.
It might be good time for it now. :-)
Bye.
--
Yasunori Goto
prev parent reply other threads:[~2006-02-10 1:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 17:04 [Lhms-devel] [RFC:PATCH(000/003)] Memory add to onlined node. (ver. 2) Luck, Tony
2006-02-09 21:39 ` [Lhms-devel] [RFC:PATCH(000/003)] Memory add to onlined node Joel Schopp
2006-02-10 1:49 ` Yasunori Goto [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=20060210103730.AFC7.Y-GOTO@jp.fujitsu.com \
--to=y-goto@jp.fujitsu.com \
--cc=ak@suse.de \
--cc=bjorn.helgaas@hp.com \
--cc=discuss@x86-64.org \
--cc=len.brown@intel.com \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.e.tolentino@intel.com \
--cc=naveen.b.s@intel.com \
--cc=tony.luck@intel.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