From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752499AbbJWBoe (ORCPT ); Thu, 22 Oct 2015 21:44:34 -0400 Received: from mga09.intel.com ([134.134.136.24]:48171 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751549AbbJWBoc convert rfc822-to-8bit (ORCPT ); Thu, 22 Oct 2015 21:44:32 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,185,1444719600"; d="scan'208";a="833067344" From: "Luck, Tony" To: "Izumi, Taku" CC: "Kamezawa, Hiroyuki" , "linux-kernel@vger.kernel.org" , "linux-mm@kvack.org" , "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 Thread-Topic: [PATCH] mm: Introduce kernelcore=reliable option Thread-Index: AQHRBwIk9GW9QoMBVU2IKX/NJ12AS552ShHAgAF+uICAAGZfoIAAlMoA//+Wwoo= Date: Fri, 23 Oct 2015 01:44:31 +0000 Message-ID: <322B7BFA-08FE-4A8F-B54C-86901BDB7CBD@intel.com> References: <1444915942-15281-1-git-send-email-izumi.taku@jp.fujitsu.com> <3908561D78D1C84285E8C5FCA982C28F32B5A060@ORSMSX114.amr.corp.intel.com> <5628B427.3050403@jp.fujitsu.com> <3908561D78D1C84285E8C5FCA982C28F32B5C7AE@ORSMSX114.amr.corp.intel.com>, In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org First part of each memory controller. I have two memory controllers on each node Sent from my iPhone > On Oct 22, 2015, at 18:01, Izumi, Taku wrote: > > 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 >