and now, courtesy of my handy-dandy dead CONFIG variable spotter, we
have the first in a series of posts identifying CONFIG_ variables that
don't appear to be set anywhere in the configuration process, along
with a recursive grep showing where they're referenced.
as a first example, restricting the search to the mm/ directory:
$ ../dead_config.sh mm
========== MAX_ACTIVE_REGIONS ==========
mm/page_alloc.c: #ifdef CONFIG_MAX_ACTIVE_REGIONS
mm/page_alloc.c: #define MAX_ACTIVE_REGIONS CONFIG_MAX_ACTIVE_REGIONS
mm/page_alloc.c: * MAX_ACTIVE_REGIONS determines the maxmimum number of
distinct
mm/page_alloc.c: /* Allow an architecture to set MAX_ACTIVE_REGIONS to save
memory */
mm/page_alloc.c: #define MAX_ACTIVE_REGIONS CONFIG_MAX_ACTIVE_REGIONS
mm/page_alloc.c: #define MAX_ACTIVE_REGIONS (MAX_NUMNODES*50)
mm/page_alloc.c: #define MAX_ACTIVE_REGIONS 256
mm/page_alloc.c: struct node_active_region __initdata
early_node_map[MAX_ACTIVE_REGIONS];
mm/page_alloc.c: nr_nodemap_entries,
MAX_ACTIVE_REGIONS);
mm/page_alloc.c: if (i >= MAX_ACTIVE_REGIONS) {
mm/page_alloc.c:
MAX_ACTIVE_REGIONS);
is it fair to say there's something strange going on here before i
run any more tests?
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================
-
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/
