From: Joel Schopp <jschopp@austin.ibm.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Yasunori Goto <y-goto@jp.fujitsu.com>, 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: Thu, 09 Feb 2006 15:39:22 -0600 [thread overview]
Message-ID: <43EBB68A.3040105@austin.ibm.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?
>
> Presumably there is a similar issue with hot add cpu.
>
Yes, cpu hot add has the same issue. It's really a performance issue,
not a functional one so you haven't seen people beating down the doors
to fix it.
Technically there isn't anything but manpower standing in the way of
doing it. But it is a good amount of work for the little it gains.
-Joel
next prev parent reply other threads:[~2006-02-09 21:39 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 ` Joel Schopp [this message]
2006-02-10 1:49 ` 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=43EBB68A.3040105@austin.ibm.com \
--to=jschopp@austin.ibm.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 \
--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