From: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
To: Andrea Arcangeli <aarcange@redhat.com>, Andi Kleen <andi@firstfloor.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Huang Ying <ying.huang@intel.com>,
Jin Dongming <jin.dongming@np.css.fujitsu.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] THP: page collapsing vs. poisoning
Date: Thu, 17 Mar 2011 11:30:12 +0900 [thread overview]
Message-ID: <4D817234.9070106@jp.fujitsu.com> (raw)
This patch set will improve system availability by allowing us to
avoid system panic in some special cases during page collapsing:
replacing a chunk of normal pages by a THP(Transparent Huge Page).
Hidetoshi Seto (4):
Lock the new THP when collapsing pages
Free the collapsed pages after the new THP is mapped.
Check whether pages are poisoned before copying
Check whether the new THP is poisoned before it is mapped to APL.
mm/huge_memory.c | 75 ++++++++++++++++++++++++++++++++++++++++++++++-------
1 files changed, 65 insertions(+), 10 deletions(-)
next reply other threads:[~2011-03-17 2:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 2:30 Hidetoshi Seto [this message]
2011-03-17 2:31 ` [PATCH 1/4] Lock the new THP when collapsing pages Hidetoshi Seto
2011-03-17 2:32 ` [PATCH 2/4] Free the collapsed pages after the new THP is mapped Hidetoshi Seto
2011-03-17 2:32 ` [PATCH 3/4] Check whether pages are poisoned before copying Hidetoshi Seto
2011-03-17 4:14 ` Andi Kleen
2011-03-17 5:20 ` Hidetoshi Seto
2011-03-17 6:26 ` Andi Kleen
2011-03-17 7:43 ` Hidetoshi Seto
2011-03-17 14:04 ` Andrea Arcangeli
2011-03-17 15:25 ` Andi Kleen
2011-03-17 16:12 ` Andrea Arcangeli
2011-03-17 16:27 ` Andi Kleen
2011-03-17 16:47 ` Andrea Arcangeli
2011-03-17 22:55 ` Andi Kleen
2011-03-23 17:26 ` K.Prasad
2011-03-23 17:32 ` Andi Kleen
2011-03-17 15:21 ` Andi Kleen
2011-03-18 5:26 ` Jin Dongming
2011-03-17 2:33 ` [PATCH 4/4] Check whether the new THP is poisoned before it is mapped to APL Hidetoshi Seto
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=4D817234.9070106@jp.fujitsu.com \
--to=seto.hidetoshi@jp.fujitsu.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=jin.dongming@np.css.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ying.huang@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;
as well as URLs for NNTP newsgroup(s).