[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <E86EADE93E2D054CBCD4E708C38D364A5427EA26@G01JPEXMBYT01>
Date: Wed, 14 Oct 2015 01:19:47 +0000
From: "Izumi, Taku" <izumi.taku@...fujitsu.com>
To: "Luck, Tony" <tony.luck@...el.com>, Xishi Qiu <qiuxishi@...wei.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"mel@....ul.ie" <mel@....ul.ie>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"Kamezawa, Hiroyuki" <kamezawa.hiroyu@...fujitsu.com>,
"Hansen, Dave" <dave.hansen@...el.com>,
"Mel Gorman" <mgorman@...e.de>, Ingo Molnar <mingo@...nel.org>
Subject: RE: [PATCH][RFC] mm: Introduce kernelcore=reliable option
> > 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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists