From: Prarit Bhargava <prarit@redhat.com>
To: chen gong <gong.chen@linux.intel.com>
Cc: ykzhao <yakui.zhao@intel.com>, Matthew Garrett <mjg@redhat.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
trenn@novell.com
Subject: Re: [RFC PATCH]: ACPI: Automatically online hot-added memory
Date: Thu, 11 Mar 2010 06:25:07 -0500 [thread overview]
Message-ID: <4B98D313.4080509@redhat.com> (raw)
In-Reply-To: <4B98AA89.4060609@linux.intel.com>
chen gong wrote:
> On 2010-3-11 16:07, ykzhao wrote:
>
>> On Thu, 2010-03-11 at 10:18 +0800, Prarit Bhargava wrote:
>>
>>>> Yes. The nehalem processor has the integrated memory controller. But it
>>>> is not required that the hot-added memory should be onlined before
>>>> bringing up CPU.
>>>> I do the following memory-hotplug test on one Machine.
>>>> a. Before hot plugging memory, four CPUs socket are installed and
>>>> all the logical CPU are brought up. (Only one node has the memory)
>>>> b. The memory is hot-plugged and then the memory is onlined so that
>>>> it can be accessed by the system.
>>>>
>>>> In the above testing case the CPU is brought up before onlining the
>>>> hot-added memory. And the test shows that it can work well.
>>>>
>>>>
>>> That doesn't work when you have multiple nodes AFAICT. The cpus do not
>>> come into service because of a lack of memory on the node.... per node
>>> allocations will fail.
>>>
>> In the test the system has multiple nodes. The reason is that the cpu
>> without memory can turn to other node and allocate the memory.
>>
>
> I agree with Yakui. The memory and CPU are irrelevant in some way. CPU can
> get memory from other nodes if it hasn't local memory, though for now it has some issues.
> Andi is working on it now (http://lkml.org/lkml/2010/2/3/343)
>
Right -- I'm working with Andi on this to get RHEL working. So I have
his slab patches, etc.. That's one of the reasons it isn't working
right now.
> BTW, how about using UDEV rules to do this operation. It looks more smooth. I know some
> Novell guy is working on it.
>
>
I was thinking about that, but the CPU comes online automatically, so
why not memory? It seems to be a discrepancy between the two. And ...
the two of you still aren't considering the obvious performance hit
which I would think makes this a must have.
P.
>
next prev parent reply other threads:[~2010-03-11 11:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 14:12 [RFC PATCH]: ACPI: Automatically online hot-added memory Prarit Bhargava
2010-03-09 15:42 ` Matthew Garrett
2010-03-09 18:27 ` Prarit Bhargava
2010-03-10 1:57 ` ykzhao
2010-03-10 13:28 ` Prarit Bhargava
2010-03-11 0:55 ` ykzhao
2010-03-11 2:18 ` Prarit Bhargava
2010-03-11 8:07 ` ykzhao
2010-03-11 8:32 ` chen gong
2010-03-11 11:25 ` Prarit Bhargava [this message]
2010-03-12 13:18 ` Thomas Renninger
2010-03-17 18:47 ` Prarit Bhargava
2010-03-19 16:55 ` Thomas Renninger
2010-03-19 17:23 ` Prarit Bhargava
2010-03-20 20:51 ` Thomas Renninger
2010-03-24 14:40 ` Thomas Renninger
2010-03-24 15:16 ` Prarit Bhargava
2010-03-11 11:18 ` Prarit Bhargava
2010-03-12 1:31 ` ykzhao
2010-03-12 13:01 ` Thomas Renninger
2010-03-17 15:24 ` Prarit Bhargava
2010-03-09 19:10 ` Alex Chiang
2010-03-09 19:10 ` Alex Chiang
2010-03-09 19:15 ` Prarit Bhargava
2010-03-09 19:15 ` Prarit Bhargava
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=4B98D313.4080509@redhat.com \
--to=prarit@redhat.com \
--cc=gong.chen@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=trenn@novell.com \
--cc=yakui.zhao@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.