RE: [PATCH] mm: Introduce kernelcore=reliable option
From: Izumi, Taku
Date: Thu Oct 22 2015 - 21:01:23 EST
Dear Tony,
> -----Original Message-----
> From: Luck, Tony [mailto:tony.luck@xxxxxxxxx]
> Sent: Friday, October 23, 2015 8:27 AM
> To: Kamezawa, Hiroyuki/亀澤 寛之; Izumi, Taku/泉 拓; linux-kernel@xxxxxxxxxxxxxxx; linux-mm@xxxxxxxxx
> Cc: qiuxishi@xxxxxxxxxx; mel@xxxxxxxxx; akpm@xxxxxxxxxxxxxxxxxxxx; Hansen, Dave; matt@xxxxxxxxxxxxxxxxxxx
> 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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/