From: jbarnes@sgi.com (Jesse Barnes)
To: linux-ia64@vger.kernel.org
Subject: Re: [Discontig-devel] [RFC/PATCH] discontig update for linux-ia64-2.5 bk tree
Date: Wed, 18 Jun 2003 17:10:40 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105595624919489@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105595612419340@msgid-missing>
On Wed, Jun 18, 2003 at 09:54:40AM -0700, Martin J. Bligh wrote:
>
> You seem to have missed the comments here:
>
> > -#ifndef CONFIG_DISCONTIGMEM /* Don't use mapnrs, do it properly */
> > extern unsigned long max_mapnr;
> > -#endif
> > ...
> > -#ifndef CONFIG_DISCONTIGMEM
> > /* The array of struct pages - for discontigmem use pgdat->lmem_map */
> > extern struct page *mem_map;
> > -#endif
>
> Using global mapnrs for discontigmem is a horrible kludge, and very
> confusing. There was a damned good reason I removed those ...
>
> It should be easy to just use local offsets into the node, right?
I'll look at this.
> > diff -Nru a/mm/page_alloc.c b/mm/page_alloc.c
> > --- a/mm/page_alloc.c Tue Jun 17 14:45:16 2003
> > +++ b/mm/page_alloc.c Tue Jun 17 14:45:16 2003
> > @@ -57,12 +57,15 @@
> > */
> > static int bad_range(struct zone *zone, struct page *page)
> > {
> > - if (page_to_pfn(page) >= zone->zone_start_pfn + zone->spanned_pages)
> > + if (page_to_pfn(page) >= zone->zone_start_pfn + zone->spanned_pages) {
> > return 1;
> > - if (page_to_pfn(page) < zone->zone_start_pfn)
> > + }
> > + if (page_to_pfn(page) < zone->zone_start_pfn) {
> > return 1;
> > - if (zone != page_zone(page))
> > + }
> > + if (zone != page_zone(page)) {
> > return 1;
> > + }
> > return 0;
> > }
>
> Why? this just looks like removing standard Linux style?
> Is there a real change hidden in there?
Oops, that one stuck past me.
Thanks,
Jesse
prev parent reply other threads:[~2003-06-18 17:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-18 16:54 [Discontig-devel] [RFC/PATCH] discontig update for linux-ia64-2.5 bk tree Martin J. Bligh
2003-06-18 17:10 ` Jesse Barnes [this message]
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=marc-linux-ia64-105595624919489@msgid-missing \
--to=jbarnes@sgi.com \
--cc=linux-ia64@vger.kernel.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