From: "Bart Van Assche" <bart.vanassche@gmail.com>
To: Mel Gorman <mel@csn.ul.ie>
Cc: Andrew Morton <akpm@linux-foundation.org>,
bugme-daemon@bugzilla.kernel.org, linux-mm@kvack.org,
Andy Whitcroft <apw@shadowen.org>
Subject: Re: [Bug 9941] New: Zone "Normal" missing in /proc/zoneinfo
Date: Wed, 13 Feb 2008 16:32:23 +0100 [thread overview]
Message-ID: <e2e108260802130732k2fdb69dckf60dd64353fb9dc7@mail.gmail.com> (raw)
In-Reply-To: <20080213143406.GA1328@csn.ul.ie>
On Feb 13, 2008 3:34 PM, Mel Gorman <mel@csn.ul.ie> wrote:
> 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?
Update: after rebooting into 2.6.24 I get now the same results with
2.6.24 and 2.6.24.2:
$ uname -a
Linux INF012 2.6.24 #1 SMP Wed Feb 13 16:16:07 CET 2008 x86_64 GNU/Linux
$ grep zone /proc/zoneinfo
Node 0, zone DMA
Node 0, zone DMA32
The output I included in the original bug report was probably from
another system with 2.6.24 that is running here, a system with 4 GB
memory instead of 2 GB. Sorry for the confusion I created.
Bart Van Assche.
--
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 15:32 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
2008-02-13 15:32 ` Bart Van Assche [this message]
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=e2e108260802130732k2fdb69dckf60dd64353fb9dc7@mail.gmail.com \
--to=bart.vanassche@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
/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).