Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Kanoj Sarcar <kanoj@google.engr.sgi.com>
To: ralf@oss.sgi.com (Ralf Baechle)
Cc: macro@ds2.pg.gda.pl (Maciej W. Rozycki),
	flo@rfc822.org (Florian Lohoff),
	linux-mips@oss.sgi.com, kanoj@engr.sgi.com (Kanoj Sarcar)
Subject: Re: crash in __alloc_bootmem_core on SGI current cvs
Date: Wed, 17 Jan 2001 05:15:36 -0800 (PST)	[thread overview]
Message-ID: <200101171315.FAA98450@google.engr.sgi.com> (raw)
In-Reply-To: <20010116172235.A1379@bacchus.dhis.org> from "Ralf Baechle" at Jan 16, 2001 05:22:35 PM

> 
> On Tue, Jan 16, 2001 at 05:39:40PM +0100, Maciej W. Rozycki wrote:
> 
> > > 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;
> > 
> >  It look reasonable but is it what was really intended?  You should ask
> > the author or linux-kernel, I suppose. 
> 
> Which probably is Kanoj who is subscribed to this list.
> 
>   Ralf
> 

realsize is fine, and that is what it is in Linus' tree. We want
to report actual number of pages, not number of pages including
the holes in memory.

Kanoj

WARNING: multiple messages have this Message-ID (diff)
From: Kanoj Sarcar <kanoj@google.engr.sgi.com>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
	Florian Lohoff <flo@rfc822.org>,
	linux-mips@oss.sgi.com, Kanoj Sarcar <kanoj@engr.sgi.com>
Subject: Re: crash in __alloc_bootmem_core on SGI current cvs
Date: Wed, 17 Jan 2001 05:15:36 -0800 (PST)	[thread overview]
Message-ID: <200101171315.FAA98450@google.engr.sgi.com> (raw)
Message-ID: <20010117131536.QlUQ3xR2D6tmn0CT2TDE4nugeBxVuZlOOCqwnpPRZ0A@z> (raw)
In-Reply-To: <20010116172235.A1379@bacchus.dhis.org> from "Ralf Baechle" at Jan 16, 2001 05:22:35 PM

> 
> On Tue, Jan 16, 2001 at 05:39:40PM +0100, Maciej W. Rozycki wrote:
> 
> > > 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;
> > 
> >  It look reasonable but is it what was really intended?  You should ask
> > the author or linux-kernel, I suppose. 
> 
> Which probably is Kanoj who is subscribed to this list.
> 
>   Ralf
> 

realsize is fine, and that is what it is in Linus' tree. We want
to report actual number of pages, not number of pages including
the holes in memory.

Kanoj

  reply	other threads:[~2001-01-17 13:20 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
2001-01-16 16:39           ` Maciej W. Rozycki
2001-01-16 19:22             ` Ralf Baechle
2001-01-17 13:15               ` Kanoj Sarcar [this message]
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=200101171315.FAA98450@google.engr.sgi.com \
    --to=kanoj@google.engr.sgi.com \
    --cc=flo@rfc822.org \
    --cc=kanoj@engr.sgi.com \
    --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