* dead CONFIG variables: first in a series
@ 2007-05-02 19:27 Robert P. J. Day
0 siblings, 0 replies; only message in thread
From: Robert P. J. Day @ 2007-05-02 19:27 UTC (permalink / raw)
To: Linux Kernel Mailing List
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
========================================================================
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2007-05-02 19:28 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-05-02 19:27 dead CONFIG variables: first in a series Robert P. J. Day
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®