Re: mem_map definition / declaration.

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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- [PATCH] mem_map is part of the FLATMEM model
  - From: Andy Whitcroft <[email protected]>

References:
- mem_map definition / declaration.
  - From: Ralf Baechle <[email protected]>

Prev by Date: Re: [PATCH] Sparsemem build fix.
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: [PATCH] mem_map is part of the FLATMEM model
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]