linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Yong Zhang <yong.zhang@windriver.com>
To: Ryan Wang <openspace.wang@gmail.com>
Cc: kernelnewbies@nl.linux.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: question about CONFIG_BASE_SMALL
Date: Wed, 4 Aug 2010 16:59:48 +0800	[thread overview]
Message-ID: <20100804085948.GA21549@windriver.com> (raw)
In-Reply-To: <AANLkTi=1DxqLrqVbfRouOBRWg4RHFaHz438X7F1JWL6P@mail.gmail.com>

On Wed, Aug 04, 2010 at 04:38:12PM +0800, Ryan Wang wrote:
> Hi all,
> 
>       I noticed CONFIG_BASE_SMALL in different parts
> of the kernel code, with ifdef/ifndef.
>       I wonder what does CONFIG_BASE_SMALL mean?
> And how can I configure it, e.g. through make menuconfig?

Yeah, here:

init/Kconfig:
...
config BASE_SMALL
	int
	default 0 if BASE_FULL
	default 1 if !BASE_FULL
...
config BASE_FULL
	default y
	bool "Enable full-sized data structures for core" if EMBEDDED
	help
	  Disabling this option reduces the size of miscellaneous core
	  kernel data structures. This saves memory on small machines,

> 
> thanks,
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2010-08-04  8:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-04  8:38 Ryan Wang
2010-08-04  8:59 ` Yong Zhang [this message]
2010-08-04  9:14 ` Mulyadi Santosa
2010-08-05  1:10   ` Pei Lin

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=20100804085948.GA21549@windriver.com \
    --to=yong.zhang@windriver.com \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=openspace.wang@gmail.com \
    /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