linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mel Gorman <mel@csn.ul.ie>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Bart Van Assche <bart.vanassche@gmail.com>,
	bugme-daemon@bugzilla.kernel.org, linux-mm@kvack.org
Subject: Re: [Bug 9941] New: Zone "Normal" missing in /proc/zoneinfo
Date: Wed, 13 Feb 2008 11:52:25 +0000	[thread overview]
Message-ID: <20080213115225.GB4007@csn.ul.ie> (raw)
In-Reply-To: <20080212234522.24bed8c1.akpm@linux-foundation.org>

On (12/02/08 23:45), Andrew Morton didst pronounce:
> On Wed, 13 Feb 2008 08:39:30 +0100 "Bart Van Assche" <bart.vanassche@gmail.com> wrote:
> 
> > On Feb 12, 2008 7:06 PM, Andrew Morton <akpm@linux-foundation.org> wrote:
> > >
> > > On Tue, 12 Feb 2008 02:39:40 -0800 (PST) bugme-daemon@bugzilla.kernel.org wrote:
> > >
> > > > http://bugzilla.kernel.org/show_bug.cgi?id=9941
> > > >
> > > >            Summary: Zone "Normal" missing in /proc/zoneinfo
> > > >            Product: Memory Management
> > > >            Version: 2.5
> > > >      KernelVersion: 2.6.24.2
> > > >           Platform: All
> > > >         OS/Version: Linux
> > > >               Tree: Mainline
> > > >             Status: NEW
> > > >           Severity: normal
> > > >           Priority: P1
> > > >          Component: Other
> > > >         AssignedTo: akpm@osdl.org
> > > >         ReportedBy: bart.vanassche@gmail.com
> > > >
> > > >
> > > > Latest working kernel version: 2.6.24
> > > > Earliest failing kernel version: 2.6.24.2
> > > > Distribution: Ubuntu 7.10 server
> > > > Hardware Environment: Intel S5000PAL
> > > > Software Environment:
> > > > Problem Description:
> > > >
> > > > There is only information about the zones "DMA" and "DMA32" in /proc/zoneinfo,
> > > > not about zone "Normal".
> > > >
> > > > Steps to reproduce:
> > > >
> > > > Run the following command in a shell:
> > > > $ grep zone /proc/zoneinfo
> > > >
> > > > Output with 2.6.24:
> > > > Node 0, zone      DMA
> > > > Node 0, zone    DMA32
> > > > Node 0, zone   Normal
> > > >
> > > > Output with 2.6.24.2:
> > > > Node 0, zone      DMA
> > > > Node 0, zone    DMA32
> > > >

The greater surprise to me is that "Normal" ever appeared. The zone is empty,
why is information appearing about it? I checked the dmesg for an x86_64
machine with 1GB of RAM that was running 2.6.24 here and there is no sign
of Normal.

mel@arnold:/tmp$ grep zone zoneinfo.before 
Node 0, zone      DMA
Node 0, zone    DMA32

The loop looks like

        for (zone = node_zones; zone - node_zones < MAX_NR_ZONES; ++zone) {
                if (!populated_zone(zone))
                        continue;

It makes no sense for it to show up *unless* 2.6.24 was compiled as a 32
bit kernel by accident. Could this be the case?

> > <SNIP>
> > Zone PFN ranges:
> >   DMA             0 ->     4096
> >   DMA32        4096 ->  1048576
> >   Normal    1048576 ->  1048576
> > Movable zone start PFN for each node
> > early_node_map[6] active PFN ranges
> >     0:        0 ->      159
> >     0:      256 ->   516825
> >     0:   517019 ->   522802
> >     0:   522906 ->   522956
> >     0:   523034 ->   523046
> >     0:   523066 ->   523264
> > On node 0 totalpages: 522771
> >   DMA zone: 96 pages used for memmap
> >   DMA zone: 2170 pages reserved
> >   DMA zone: 1733 pages, LIFO batch:0
> >   DMA32 zone: 12168 pages used for memmap
> >   DMA32 zone: 506604 pages, LIFO batch:31
> >   Normal zone: 0 pages used for memmap
> >   Movable zone: 0 pages used for memmap
> 
> OK, that machine really has no ZONE_NORMAL.  I didn't know we do that.
> 

On x86_64 (which is what it is according to the config), machines with less
than 4GB of RAM will have no ZONE_NORMAL. This machine appears to have 2GB. I
don't see the problem as such because it's like PPC64 only having ZONE_DMA
(ZONE_NORMAL exists but it is always empty).

> Mel, is this, uh, normal?
> 

On x86_64, it is.

-- 
Mel Gorman
Part-time Phd Student                          Linux Technology Center
University of Limerick                         IBM Dublin Software Lab

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

  reply	other threads:[~2008-02-13 11:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-9941-27@http.bugzilla.kernel.org/>
2008-02-12 18:06 ` [Bug 9941] New: Zone "Normal" missing in /proc/zoneinfo Andrew Morton
2008-02-13  7:39   ` Bart Van Assche
2008-02-13  7:45     ` Andrew Morton
2008-02-13 11:52       ` Mel Gorman [this message]
2008-02-13 13:45         ` Bart Van Assche
2008-02-13 14:34           ` Mel Gorman
2008-02-13 15:32             ` Bart Van Assche
2008-02-13 15:23         ` Andy Whitcroft
2008-02-13 15:38           ` Mel Gorman

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=20080213115225.GB4007@csn.ul.ie \
    --to=mel@csn.ul.ie \
    --cc=akpm@linux-foundation.org \
    --cc=bart.vanassche@gmail.com \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).