From: Florian Lohoff <flo@rfc822.org>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Ralf Baechle <ralf@oss.sgi.com>, linux-mips@oss.sgi.com
Subject: Re: crash in __alloc_bootmem_core on SGI current cvs
Date: Tue, 16 Jan 2001 17:28:12 +0100 [thread overview]
Message-ID: <20010116172812.B7327@paradigm.rfc822.org> (raw)
In-Reply-To: <Pine.GSO.3.96.1010116170209.5546K-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Tue, Jan 16, 2001 at 05:06:29PM +0100
On Tue, Jan 16, 2001 at 05:06:29PM +0100, Maciej W. Rozycki wrote:
> On Tue, 16 Jan 2001, Ralf Baechle wrote:
>
> > > Before:
> > > On node 0 totalpages: 589824
> > > zone(0): 589824 pages.
> > >
> > >
> > > After:
> > > On node 0 totalpages: 65536
> > > zone(0): 65536 pages.
> >
> > I probably already got used too machines with gigs of memory to notice ;-)
>
> The number actually denotes the highest page, regardless of the number of
> pages, so you only need a single page placed far away from address zero to
> observe such large counts.
Wouldnt be this correct ? Realsize is size - holes.
Index: mm/page_alloc.c
===================================================================
RCS file: /cvs/linux/mm/page_alloc.c,v
retrieving revision 1.49
diff -u -r1.49 page_alloc.c
--- mm/page_alloc.c 2001/01/11 04:02:45 1.49
+++ mm/page_alloc.c 2001/01/16 16:26:55
@@ -824,7 +824,7 @@
if (zholes_size)
realsize -= zholes_size[j];
- printk("zone(%lu): %lu pages.\n", j, size);
+ printk("zone(%lu): %lu pages.\n", j, realsize);
zone->size = size;
zone->name = zone_names[j];
zone->lock = SPIN_LOCK_UNLOCKED;
Flo
--
Florian Lohoff flo@rfc822.org +49-5201-669912
Why is it called "common sense" when nobody seems to have any?
next prev parent reply other threads:[~2001-01-16 16:30 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-15 17:11 crash in __alloc_bootmem_core on SGI current cvs Florian Lohoff
2001-01-15 21:21 ` Maciej W. Rozycki
2001-01-16 8:10 ` Ralf Baechle
2001-01-16 14:36 ` Florian Lohoff
2001-01-16 15:57 ` Ralf Baechle
2001-01-16 16:06 ` Maciej W. Rozycki
2001-01-16 16:24 ` Ralf Baechle
2001-01-16 16:34 ` Maciej W. Rozycki
2001-01-16 19:23 ` Ralf Baechle
2001-01-16 19:47 ` Maciej W. Rozycki
2001-01-16 20:04 ` Ralf Baechle
2001-01-16 16:44 ` Florian Lohoff
2001-01-16 16:28 ` Florian Lohoff [this message]
2001-01-16 16:39 ` Maciej W. Rozycki
2001-01-16 19:22 ` Ralf Baechle
2001-01-17 13:15 ` Kanoj Sarcar
2001-01-17 13:15 ` Kanoj Sarcar
2001-01-16 16:01 ` Maciej W. Rozycki
2001-01-16 16:08 ` Maciej W. Rozycki
2001-01-16 16:49 ` Florian Lohoff
2001-01-16 18:48 ` Florian Lohoff
2001-01-16 19:52 ` Maciej W. Rozycki
2001-01-16 23:03 ` Florian Lohoff
-- strict thread matches above, loose matches on Subject: below --
2001-01-16 16:55 Ian Chilton
2001-01-16 17:06 ` Maciej W. Rozycki
2001-01-16 19:14 ` Ralf Baechle
2001-01-16 19:38 ` Maciej W. Rozycki
2001-01-16 16:56 tmaloney
2001-01-16 16:59 Ian Chilton
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=20010116172812.B7327@paradigm.rfc822.org \
--to=flo@rfc822.org \
--cc=linux-mips@oss.sgi.com \
--cc=macro@ds2.pg.gda.pl \
--cc=ralf@oss.sgi.com \
/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