public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frans Pop <elendil@planet.nl>
To: linux-kernel@vger.kernel.org
Cc: Kernel Testers List <kernel-testers@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [regression?] [resend] Memory zone info seems incomplete in boottime dmesg output
Date: Thu, 14 Aug 2008 20:42:23 +0200	[thread overview]
Message-ID: <200808142042.24606.elendil@planet.nl> (raw)

With 2.6.26 I get:
<snip>
Zone PFN ranges:
  DMA             0 ->     4096
  DMA32        4096 ->  1048576
  Normal    1048576 ->  1048576
Movable zone start PFN for each node
early_node_map[4] active PFN ranges
    0:        0 ->      159
    0:      256 ->   521844
    0:   521961 ->   521964
    0:   521983 ->   521984
On node 0 totalpages: 521751
  DMA zone: 56 pages used for memmap
  DMA zone: 1271 pages reserved
  DMA zone: 2672 pages, LIFO batch:0
  DMA32 zone: 7081 pages used for memmap
  DMA32 zone: 510671 pages, LIFO batch:31
  Normal zone: 0 pages used for memmap
  Movable zone: 0 pages used for memmap
</snip>

With 2.6.27-rc1 I only get pages listed for 2 zones (bottom part):
<snip>
Zone PFN ranges:
  DMA      0x00000000 -> 0x00001000
  DMA32    0x00001000 -> 0x00100000
  Normal   0x00100000 -> 0x00100000
Movable zone start PFN for each node
early_node_map[4] active PFN ranges
    0: 0x00000000 -> 0x0000009f
    0: 0x00000100 -> 0x0007f674
    0: 0x0007f6e9 -> 0x0007f6ec
    0: 0x0007f6ff -> 0x0007f700
On node 0 totalpages: 521751
  DMA zone: 2072 pages, LIFO batch:0
  DMA32 zone: 506625 pages, LIFO batch:31
</snip>

Note that totalpages is the same and that for 2.6.26 the sum of pages for 
all listed zones is equal to totalpages. Seems we've lost useful info 
here.

I also seem to have "lost" 600 LIFO batch pages for DMA and 4000 for DMA32 
between the kernel versions although that could be due to config changes 
(I enabled some extra debugging options). Harder to tell though without 
the info where they've gone...

Cheers,
FJP

P.S. As a user I really don't find the hex values easier to read/use than 
the decimal values. Except maybe for the "Zone PFN ranges" where things 
seem to be nicely aligned.

             reply	other threads:[~2008-08-14 18:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-14 18:42 Frans Pop [this message]
2008-08-14 19:08 ` [regression?] [resend] Memory zone info seems incomplete in boottime dmesg output Sven Wegener
2008-08-14 20:46   ` Frans Pop
2008-08-14 19:13 ` Andrew Morton
2008-08-15 10:05   ` Mel Gorman
2008-08-28 18:16     ` Paul Jackson

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=200808142042.24606.elendil@planet.nl \
    --to=elendil@planet.nl \
    --cc=akpm@linux-foundation.org \
    --cc=kernel-testers@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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