From: Haicheng Li <haicheng.li@linux.intel.com>
To: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Wu, Fengguang" <fengguang.wu@intel.com>,
Andi Kleen <andi@firstfloor.org>, Mel Gorman <mel@csn.ul.ie>,
Christoph Lameter <cl@linux-foundation.org>,
Tejun Heo <tj@kernel.org>
Subject: [PATCH 0/3] Fix boot_pageset sharing issue for new populated zones of hotadded nodes
Date: Mon, 17 May 2010 16:17:52 +0800 [thread overview]
Message-ID: <4BF0FBB0.1080707@linux.intel.com> (raw)
In our recent cpu/memory hotadd testing, with multiple nodes hotadded,
kernel easily panics under stress workload like kernel building.
The root cause is that the new populated zones of hotadded nodes are
sharing same per_cpu_pageset, i.e. boot strapping boot_pageset, which
finally causes page state wrong.
The following three patches will setup the pagesets for hotadded nodes
with dynamically allocated per_cpu_pageset struct.
---
include/linux/memory_hotplug.h | 8 +++++
include/linux/mmzone.h | 2 +-
init/main.c | 2 +-
mm/memory_hotplug.c | 27 +++++++++++-----
mm/page_alloc.c | 66 +++++++++++++++++++++++++++-------------
5 files changed, 74 insertions(+), 31 deletions(-)
--
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 reply other threads:[~2010-05-17 8:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-17 8:17 Haicheng Li [this message]
2010-05-17 10:34 ` [PATCH 0/3] Fix boot_pageset sharing issue for new populated zones of hotadded nodes Andi Kleen
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=4BF0FBB0.1080707@linux.intel.com \
--to=haicheng.li@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=cl@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=tj@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;
as well as URLs for NNTP newsgroup(s).