All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck@intel.com>
To: Xishi Qiu <qiuxishi@huawei.com>, Taku Izumi <izumi.taku@jp.fujitsu.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"kamezawa.hiroyu@jp.fujitsu.com" <kamezawa.hiroyu@jp.fujitsu.com>,
	"mel@csn.ul.ie" <mel@csn.ul.ie>,
	"Hansen, Dave" <dave.hansen@intel.com>,
	"matt@codeblueprint.co.uk" <matt@codeblueprint.co.uk>
Subject: RE: [PATCH v3 2/2] mm: Introduce kernelcore=mirror option
Date: Wed, 9 Dec 2015 21:59:17 +0000	[thread overview]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F39F7F4CD@ORSMSX114.amr.corp.intel.com> (raw)
In-Reply-To: <56679FDC.1080800@huawei.com>

> How about add some comment, if mirrored memroy is too small, then the
> normal zone is small, so it may be oom.
> The mirrored memory is at least 1/64 of whole memory, because struct
> pages usually take 64 bytes per page.

1/64th is the absolute lower bound (for the page structures as you say). I
expect people will need to configure 10% or more to run any real workloads.

I made the memblock boot time allocator fall back to non-mirrored memory
if mirrored memory ran out.  What happens in the run time allocator if the
non-movable zones run out of pages? Will we allocate kernel pages from movable
memory?

-Tony

WARNING: multiple messages have this Message-ID (diff)
From: "Luck, Tony" <tony.luck@intel.com>
To: Xishi Qiu <qiuxishi@huawei.com>, Taku Izumi <izumi.taku@jp.fujitsu.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"kamezawa.hiroyu@jp.fujitsu.com" <kamezawa.hiroyu@jp.fujitsu.com>,
	"mel@csn.ul.ie" <mel@csn.ul.ie>,
	"Hansen, Dave" <dave.hansen@intel.com>,
	"matt@codeblueprint.co.uk" <matt@codeblueprint.co.uk>
Subject: RE: [PATCH v3 2/2] mm: Introduce kernelcore=mirror option
Date: Wed, 9 Dec 2015 21:59:17 +0000	[thread overview]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F39F7F4CD@ORSMSX114.amr.corp.intel.com> (raw)
In-Reply-To: <56679FDC.1080800@huawei.com>

> How about add some comment, if mirrored memroy is too small, then the
> normal zone is small, so it may be oom.
> The mirrored memory is at least 1/64 of whole memory, because struct
> pages usually take 64 bytes per page.

1/64th is the absolute lower bound (for the page structures as you say). I
expect people will need to configure 10% or more to run any real workloads.

I made the memblock boot time allocator fall back to non-mirrored memory
if mirrored memory ran out.  What happens in the run time allocator if the
non-movable zones run out of pages? Will we allocate kernel pages from movable
memory?

-Tony

--
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>

  reply	other threads:[~2015-12-09 21:59 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09  3:18 [PATCH v3 0/2] mm: Introduce kernelcore=mirror option Taku Izumi
2015-12-09  3:18 ` Taku Izumi
2015-12-09  3:19 ` [PATCH v3 1/2] mm: Calculate zone_start_pfn at zone_spanned_pages_in_node() Taku Izumi
2015-12-09  3:19   ` Taku Izumi
2015-12-09  3:19 ` [PATCH v3 2/2] mm: Introduce kernelcore=mirror option Taku Izumi
2015-12-09  3:19   ` Taku Izumi
2015-12-09  3:28   ` Xishi Qiu
2015-12-09  3:28     ` Xishi Qiu
2015-12-09 21:59     ` Luck, Tony [this message]
2015-12-09 21:59       ` Luck, Tony
2015-12-10  1:14       ` Xishi Qiu
2015-12-10  1:14         ` Xishi Qiu
2015-12-10  5:37         ` Izumi, Taku
2015-12-10  5:37           ` Izumi, Taku
2015-12-10  6:13           ` Xishi Qiu
2015-12-10  6:13             ` Xishi Qiu
2015-12-11  5:53             ` Izumi, Taku
2015-12-11  5:53               ` Izumi, Taku
2015-12-11  9:44               ` Xishi Qiu
2015-12-11  9:44                 ` Xishi Qiu
2015-12-17  1:38                 ` Izumi, Taku
2015-12-17  1:38                   ` Izumi, Taku
2015-12-17  2:47                   ` Xishi Qiu
2015-12-17  2:47                     ` Xishi Qiu
2015-12-17  2:53                     ` Kamezawa Hiroyuki
2015-12-17  2:53                       ` Kamezawa Hiroyuki
2015-12-17  4:48                       ` Xishi Qiu
2015-12-17  4:48                         ` Xishi Qiu
2015-12-17  5:01                         ` Kamezawa Hiroyuki
2015-12-17  5:01                           ` Kamezawa Hiroyuki
2015-12-17 18:43                           ` Luck, Tony
2015-12-17 18:43                             ` Luck, Tony
2015-12-18  2:12                             ` Kamezawa Hiroyuki
2015-12-18  2:12                               ` Kamezawa Hiroyuki
2015-12-18  6:59                               ` Luck, Tony
2015-12-18  6:59                                 ` Luck, Tony
2015-12-28 22:21   ` Andrew Morton
2015-12-28 22:21     ` Andrew Morton
2015-12-28 22:32   ` Andrew Morton
2015-12-28 22:32     ` Andrew Morton

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=3908561D78D1C84285E8C5FCA982C28F39F7F4CD@ORSMSX114.amr.corp.intel.com \
    --to=tony.luck@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=dave.hansen@intel.com \
    --cc=izumi.taku@jp.fujitsu.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=matt@codeblueprint.co.uk \
    --cc=mel@csn.ul.ie \
    --cc=qiuxishi@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.