From: "Izumi, Taku" <izumi.taku@jp.fujitsu.com>
To: "Luck, Tony" <tony.luck@intel.com>, Xishi Qiu <qiuxishi@huawei.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"mel@csn.ul.ie" <mel@csn.ul.ie>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"Kamezawa, Hiroyuki" <kamezawa.hiroyu@jp.fujitsu.com>,
"Hansen, Dave" <dave.hansen@intel.com>,
Mel Gorman <mgorman@suse.de>, Ingo Molnar <mingo@kernel.org>
Subject: RE: [PATCH][RFC] mm: Introduce kernelcore=reliable option
Date: Wed, 14 Oct 2015 01:19:47 +0000 [thread overview]
Message-ID: <E86EADE93E2D054CBCD4E708C38D364A5427EA26@G01JPEXMBYT01> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F32B534D5@ORSMSX114.amr.corp.intel.com>
> > I remember Kame has already suggested this idea. In my opinion,
> > I still think it's better to add a new migratetype or a new zone,
> > so both user and kernel could use mirrored memory.
>
> A new zone would be more flexible ... and probably the right long
> term solution. But this looks like a very clever was to try out the
> feature with a minimally invasive patch.
Yes. I agree creating a new zone is the right solution for long term.
I believe this approach using MOVABLE_ZONE is good and reasonable
for short-term solution.
Sincerely,
Taku Izumi
--
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>
prev parent reply other threads:[~2015-10-14 1:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 14:56 Taku Izumi
2015-10-09 6:46 ` Xishi Qiu
2015-10-09 9:24 ` Kamezawa Hiroyuki
2015-10-09 10:36 ` Xishi Qiu
2015-10-09 15:08 ` Dave Hansen
2015-10-09 18:51 ` Luck, Tony
2015-10-12 10:32 ` Matt Fleming
2015-10-10 2:01 ` Xishi Qiu
2015-10-12 18:43 ` Luck, Tony
2015-10-13 9:51 ` Kamezawa Hiroyuki
2015-10-09 21:43 ` Luck, Tony
2015-10-14 1:19 ` Izumi, Taku [this message]
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=E86EADE93E2D054CBCD4E708C38D364A5427EA26@G01JPEXMBYT01 \
--to=izumi.taku@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=qiuxishi@huawei.com \
--cc=tony.luck@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