mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: dead CONFIG variables:  first in a series
Date: Wed, 2 May 2007 15:27:58 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0705021524070.14127@localhost.localdomain> (raw)


  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
========================================================================

                 reply	other threads:[~2007-05-02 19:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0705021524070.14127@localhost.localdomain \
    --to=rpjday@mindspring.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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®