Re: mem_map definition / declaration.

From: Andy Whitcroft <apw@xxxxxxxxxxxx>
Date: Wed, 31 May 2006 18:00:29 +0100

Ralf Baechle wrote:

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.

Sounds suspect for sure. I will take a look and see. Thanks for the
head up.

-apw
-
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/

References:
- mem_map definition / declaration.
  - From: Ralf Baechle

Prev by Date: PCI: Bus is hidden behind transparent bridge
Next by Date: [PATCH] don't automatically drop packets from 0.0.0.0/8
Previous by thread: mem_map definition / declaration.
Next by thread: Kernel 2.6.16.18 with general protection fault, perhaps nfsd
Index(es):
- Date
- Thread