From: "Izumi, Taku" <izumi.taku@jp.fujitsu.com>
To: "Luck, Tony" <tony.luck@intel.com>,
"Kamezawa, Hiroyuki" <kamezawa.hiroyu@jp.fujitsu.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Cc: "qiuxishi@huawei.com" <qiuxishi@huawei.com>,
"mel@csn.ul.ie" <mel@csn.ul.ie>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"Hansen, Dave" <dave.hansen@intel.com>,
"matt@codeblueprint.co.uk" <matt@codeblueprint.co.uk>
Subject: RE: [PATCH] mm: Introduce kernelcore=reliable option
Date: Fri, 23 Oct 2015 01:01:12 +0000 [thread overview]
Message-ID: <E86EADE93E2D054CBCD4E708C38D364A54280C26@G01JPEXMBYT01> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F32B5C7AE@ORSMSX114.amr.corp.intel.com>
Dear Tony,
> -----Original Message-----
> From: Luck, Tony [mailto:tony.luck@intel.com]
> Sent: Friday, October 23, 2015 8:27 AM
> To: Kamezawa, Hiroyuki/亀澤 寛之; Izumi, Taku/泉 拓; linux-kernel@vger.kernel.org; linux-mm@kvack.org
> Cc: qiuxishi@huawei.com; mel@csn.ul.ie; akpm@linux-foundation.org; Hansen, Dave; matt@codeblueprint.co.uk
> Subject: RE: [PATCH] mm: Introduce kernelcore=reliable option
>
> > I think /proc/zoneinfo can show detailed numbers per zone. Do we need some for meminfo ?
>
> I wrote a little script (attached) to summarize /proc/zoneinfo ... on my system it says
>
> $ zoneinfo
> Node Normal Movable DMA DMA32
> 0 0.00 103020.07 8.94 1554.46
> 1 9284.54 89870.43
> 2 9626.33 94050.09
> 3 9602.82 93650.04
>
> Not sure why I have zero Normal memory free on node0. The sum of all those
> free counts is 410667.72 MB ... which is close enough to the boot time message
> showing the amount of mirror/total memory:
>
> [ 0.000000] efi: Memory: 80979/420096M mirrored memory
>
> but a fair amount of the 80G of mirrored memory seems to have been miscounted
> as Movable instead of Normal. Perhaps this is because I have two blocks of mirrored
> memory on each node and the movable zone code doesn't expect that?
You were saying that OS view of memory of node is something like the following ?
Node X: |MMMMMM------MMMMMM--------|
(legend) M: mirrored -: not mirrrored
If so, is this a real Box's configuration?
Sorry, I haven't got a real Address Range Mirror capable boxes yet ...
I thought mirroring range is concatenated at the first part of each node.
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>
next prev parent reply other threads:[~2015-10-23 1:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 13:32 Taku Izumi
2015-10-19 2:25 ` Xishi Qiu
2015-10-20 0:34 ` Izumi, Taku
2015-10-20 1:42 ` Xishi Qiu
2015-10-21 18:17 ` Luck, Tony
2015-10-22 10:02 ` Kamezawa Hiroyuki
2015-10-22 23:26 ` Luck, Tony
2015-10-23 1:01 ` Izumi, Taku [this message]
2015-10-23 1:44 ` Luck, Tony
2015-10-30 6:19 ` Kamezawa Hiroyuki
2015-10-30 19:42 ` Luck, Tony
2015-11-04 6:56 ` Kamezawa Hiroyuki
2015-10-23 3:36 ` Xishi Qiu
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=E86EADE93E2D054CBCD4E708C38D364A54280C26@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=matt@codeblueprint.co.uk \
--cc=mel@csn.ul.ie \
--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