linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck@intel.com>
To: Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Xishi Qiu <qiuxishi@huawei.com>
Cc: "Izumi, Taku" <izumi.taku@jp.fujitsu.com>,
	"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>,
	"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: Fri, 18 Dec 2015 06:59:08 +0000	[thread overview]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F39F88DAC@ORSMSX114.amr.corp.intel.com> (raw)
In-Reply-To: <56736B7D.3040709@jp.fujitsu.com>

>Hmm...like this ?
>       sysctl.vm.fallback_mirror_memory = 0  // never fallback  # default.
>       sysctl.vm.fallback_mirror_memory = 1  // the user memory may be allocated from mirrored zone.
>       sysctl.vm.fallback_mirror_memory = 2  // usually kernel allocates memory from mirrored zone before OOM.
>       sysctl.vm.fallback_mirror_memory = 3  // 1+2

Should option 2 say: // allow kernel to allocate from non-mirror zone to avoid OOM

> However I believe my customer's choice is always 0, above implementation can be done in a clean way.
> (adding a flag to zones (mirrored or not) and controlling fallback zonelist walk.)

Modes allow us to make all of the people happy (I hope).

> BTW, we need this Taku's patch to make a progress. I think other devs should be done in another
> development cycle. What does he need to get your Acks ?

The concept is great.   It's even "Tested-by: Tony Luck <tony.luck@intel.com>".
I need to read the code more carefully before Acked-by.

-Tony

  reply	other threads:[~2015-12-18  6:59 UTC|newest]

Thread overview: 20+ 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:19 ` [PATCH v3 1/2] mm: Calculate zone_start_pfn at zone_spanned_pages_in_node() Taku Izumi
2015-12-09  3:19 ` [PATCH v3 2/2] mm: Introduce kernelcore=mirror option Taku Izumi
2015-12-09  3:28   ` Xishi Qiu
2015-12-09 21:59     ` Luck, Tony
2015-12-10  1:14       ` Xishi Qiu
2015-12-10  5:37         ` Izumi, Taku
2015-12-10  6:13           ` Xishi Qiu
2015-12-11  5:53             ` Izumi, Taku
2015-12-11  9:44               ` Xishi Qiu
2015-12-17  1:38                 ` Izumi, Taku
2015-12-17  2:47                   ` Xishi Qiu
2015-12-17  2:53                     ` Kamezawa Hiroyuki
2015-12-17  4:48                       ` Xishi Qiu
2015-12-17  5:01                         ` Kamezawa Hiroyuki
2015-12-17 18:43                           ` Luck, Tony
2015-12-18  2:12                             ` Kamezawa Hiroyuki
2015-12-18  6:59                               ` Luck, Tony [this message]
2015-12-28 22:21   ` 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=3908561D78D1C84285E8C5FCA982C28F39F88DAC@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 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).