linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck@intel.com>
To: Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Taku Izumi <izumi.taku@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: Thu, 22 Oct 2015 23:26:49 +0000	[thread overview]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F32B5C7AE@ORSMSX114.amr.corp.intel.com> (raw)
In-Reply-To: <5628B427.3050403@jp.fujitsu.com>

[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]

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

-Tony                             




[-- Attachment #2: zoneinfo --]
[-- Type: application/octet-stream, Size: 485 bytes --]

#!/bin/bash

awk '
$1 == "Node" {
	thisnode = $2 + 0
	thiszone = $4
	allnodes[thisnode] = thisnode
	znames[thiszone] = 1
}
$1 == "pages" && $2 == "free" {
	nfree[thisnode "," thiszone] = $3
}
END {
	printf("Node ")
	for (z in znames)
		printf("%15s ", z)
	printf("\n")

	for (n in allnodes) {
		printf("%4d ", n)
		for (z in znames) {
			idx = n "," z
			if (idx in nfree)
				printf("%15.2f ", nfree[idx]/256.0)
			else
				printf("%15s ", "")
		}
		printf("\n")
	}
}' /proc/zoneinfo

  reply	other threads:[~2015-10-22 23:27 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 [this message]
2015-10-23  1:01       ` Izumi, Taku
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=3908561D78D1C84285E8C5FCA982C28F32B5C7AE@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