From: Mel Gorman <mel@csn.ul.ie>
To: Bart Van Assche <bart.vanassche@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
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 14:34:07 +0000 [thread overview]
Message-ID: <20080213143406.GA1328@csn.ul.ie> (raw)
In-Reply-To: <e2e108260802130545u3086fbecn2793aab64b895a74@mail.gmail.com>
On (13/02/08 14:45), Bart Van Assche didst pronounce:
> On Feb 13, 2008 12:52 PM, <bugme-daemon@bugzilla.kernel.org> wrote:
> > http://bugzilla.kernel.org/show_bug.cgi?id=9941
> >
> > 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.
>
> Both tests were performed with the kernel compiled for x86_64 and were
> run on the same system. I was surprised to see a difference in the
> zoneinfo between 2.6.24 and 2.6.24.2 kernels.
You are not the only one. I boot-tested an x86_64 machine with 3GB of
RAM which is as close as was available to yours and I got
root@elm3a188:~# uname -r
2.6.24-autokern1
root@elm3a188:~# free -m
total used free shared buffers cached
Mem: 2988 83 2904 0 2 28
-/+ buffers/cache: 52 2935
Swap: 15633 0 15633
root@elm3a188:~# grep zone /proc/zoneinfo
Node 0, zone DMA
Node 0, zone DMA32
No sign of ZONE_NORMAL there.
> But if I understand you
> correctly then the 2.6.24.2 behavior is the only correct behavior ?
>
Yes. You should not be seeing a Normal zone unless you have > 4GB of
RAM unless for some really strange reason your physical memory was
placed above the 4GB mark which is possibly but unlikely. Could you post
the dmesg -s 1000000 of 2.6.24 and its .config just in case please?
--
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>
next prev parent reply other threads:[~2008-02-13 14:34 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
2008-02-13 13:45 ` Bart Van Assche
2008-02-13 14:34 ` Mel Gorman [this message]
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=20080213143406.GA1328@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).