mem_map definition / declaration.
- From: Ralf Baechle <ralf@xxxxxxxxxxxxxx>
- Date: Wed, 31 May 2006 17:23:45 +0100
mm/memory defines mem_map and max_mapnr only if !CONFIG_NEED_MULTIPLE_NODES.
<linux/mm.h> declares mem_map[] if !CONFIG_DISCONTIGMEM. Shouldn't
both depend on !CONFIG_FLATMEM? As things are now mem_map may be
declared but not defined for a non-NUMA sparsemem system which may make
tracking a remaining mem_map reference in the code a little harder.
Ralf
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: mem_map definition / declaration.
- From: Andy Whitcroft
- Re: mem_map definition / declaration.
- Prev by Date: Re: [rfc][patch] remove racy sync_page?
- Next by Date: Re: [rfc][patch] remove racy sync_page?
- Previous by thread: [PATCH 3/11] 2.6.17-rc5 perfmon2 patch for review: new generic header files
- Next by thread: Re: mem_map definition / declaration.
- Index(es):
Relevant Pages
|
