From: Nishanth Aravamudan <nacc@us.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Christoph Lameter <clameter@sgi.com>,
kxr@sgi.com, Lee Schermerhorn <Lee.Schermerhorn@hp.com>,
Bob Picco <bob.picco@hp.com>,
linux-mm@kvack.org,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Mel Gorman <mel@skynet.ie>
Subject: Re: [patch 02/14] Memoryless nodes: introduce mask of nodes with memory
Date: Wed, 8 Aug 2007 12:55:14 -0700 [thread overview]
Message-ID: <20070808195514.GE16588@us.ibm.com> (raw)
In-Reply-To: <20070808123804.d3b3bc79.akpm@linux-foundation.org>
On 08.08.2007 [12:38:04 -0700], Andrew Morton wrote:
> On Fri, 03 Aug 2007 20:01:02 -0700
> Christoph Lameter <clameter@sgi.com> wrote:
>
> > +/* Any regular memory on that node ? */
> > +static void check_for_regular_memory(pg_data_t *pgdat)
> > +{
> > +#ifdef CONFIG_HIGHMEM
> > + enum zone_type zone;
> > +
> > + for (zone = 0; zone <= ZONE_NORMAL; zone++)
> > + if (pgdat->node_zones[zone].present_pages)
> > + node_set_state(nid, N_NORMAL_MEMORY);
> > + }
> > +#endif
> > +}
>
> mm/page_alloc.c: In function 'check_for_regular_memory':
> mm/page_alloc.c:2427: error: 'nid' undeclared (first use in this function)
> mm/page_alloc.c:2427: error: (Each undeclared identifier is reported only once
> mm/page_alloc.c:2427: error: for each function it appears in.)
> mm/page_alloc.c: At top level:
> mm/page_alloc.c:2430: error: expected identifier or '(' before '}' token
>
> OK, easily fixable with
>
> /* Any regular memory on that node ? */
> static void check_for_regular_memory(pg_data_t *pgdat)
> {
> #ifdef CONFIG_HIGHMEM
> enum zone_type zone_type;
>
> for (zone_type = 0; zone_type <= ZONE_NORMAL; zone_type++) {
> struct zone *zone = &pgdat->node_zones[zone_type];
> if (zone->present_pages)
> node_set_state(zone_to_nid(zone), N_NORMAL_MEMORY);
> }
> #endif
> }
>
> but we continue to have some significant testing issues out there.
This would be because the patch that Christoph submitted here is not the
same as the patch that Mel and I tested...There was no
check_for_regular_memory() function in the kernels I was building.
Thanks,
Nish
--
Nishanth Aravamudan <nacc@us.ibm.com>
IBM Linux Technology Center
--
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:[~2007-08-08 19:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070804030100.862311140@sgi.com>
2007-08-04 3:18 ` [patch 00/14] NUMA: Memoryless node support V3 Nishanth Aravamudan
[not found] ` <20070804030152.843011254@sgi.com>
2007-08-08 19:38 ` [patch 02/14] Memoryless nodes: introduce mask of nodes with memory Andrew Morton
2007-08-08 19:55 ` Nishanth Aravamudan [this message]
2007-08-08 20:03 ` Nishanth Aravamudan
2007-08-08 20:05 ` Christoph Lameter
2007-08-08 23:35 ` Nishanth Aravamudan
2007-08-08 20:04 ` Christoph Lameter
2007-07-27 19:43 [PATCH 00/14] NUMA: Memoryless node support V4 Lee Schermerhorn
2007-07-27 19:43 ` [PATCH 02/14] Memoryless nodes: introduce mask of nodes with memory Lee Schermerhorn
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=20070808195514.GE16588@us.ibm.com \
--to=nacc@us.ibm.com \
--cc=Lee.Schermerhorn@hp.com \
--cc=akpm@linux-foundation.org \
--cc=bob.picco@hp.com \
--cc=clameter@sgi.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kxr@sgi.com \
--cc=linux-mm@kvack.org \
--cc=mel@skynet.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