From: Andrew Morton <akpm@linux-foundation.org>
To: minskey guo <chaohong_guo@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@vger.kernel.org, "Kleen,
Andi" <andi.kleen@intel.com>
Subject: Re: [PATCH] CPU/mem hotplug: enable CPUs online before local memory online
Date: Fri, 7 May 2010 13:50:42 -0700 [thread overview]
Message-ID: <20100507135042.5710d330.akpm@linux-foundation.org> (raw)
In-Reply-To: <4BE3AA3C.4080507@linux.intel.com>
On Fri, 07 May 2010 13:50:52 +0800
minskey guo <chaohong_guo@linux.intel.com> wrote:
> This patch enables users to online CPUs even if the CPUs belongs to
> a numa node which doesn't have onlined local memory.
>
> The zonlists(pg_data_t.node_zonelists[]) of a numa node are created
> either in system boot/init period, or at the time of local memory
> online. For a numa node without onlined local memory, its zonelists
> are not initialized at present. As a result, any memory allocation
> operations executed by CPUs within this node will fail. In fact, an
> out-of-memory error is triggered when attempt to online CPUs before
> memory comes to online.
>
> This patch tries to create zonelists for such numa nodes, so that
> the memory allocation for this node can be fallback'ed to other
> nodes.
I had a horrible time extracting a usable patch from this email.
Please don't send two copies of a patch in a single email. One version
was space-stuffed and the other had text/plain mimetype. text/plain
attachents are OK. Plain old inlined text is preferred, but first
email yourself a test patch to check that it isn't getting mangled.
Make sure that the patch has lines longer than 100 chars to check for
wordwrapping.
I removed the unneeded EXPORT_SYMBOL_GPL(mem_online_node);
parent reply other threads:[~2010-05-07 20:50 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <4BE3AA3C.4080507@linux.intel.com>]
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=20100507135042.5710d330.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andi.kleen@intel.com \
--cc=chaohong_guo@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@vger.kernel.org \
/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
all inboxes | Powered by JetHome®