From: Matt Mackall <mpm@selenic.com>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/8] base-small: CONFIG_BASE_SMALL for small systems
Date: Mon, 31 Jan 2005 20:18:58 -0800 [thread overview]
Message-ID: <20050201041858.GT2891@waste.org> (raw)
In-Reply-To: <200502010055.j110tWbd022651@laptop11.inf.utfsm.cl>
On Mon, Jan 31, 2005 at 09:55:32PM -0300, Horst von Brand wrote:
> Matt Mackall <mpm@selenic.com> said:
> > This patch series introduced a new pair of CONFIG_EMBEDDED options call
> > CONFIG_BASE_FULL/CONFIG_BASE_SMALL. Disabling CONFIG_BASE_FULL sets
> > the boolean CONFIG_BASE_SMALL to 1 and it is used to shrink a number
> > of core data structures. The space savings for the current batch is
> > around 14k.
>
> Why _two_ config options?
Um, Andrew made me do it?
One option is an int and is used thusly:
#define FOO (CONFIG_BASE_SMALL ? 1 : 1000)
But it's also sometimes useful to have two opposing options so that
you can use:
obj-(CONFIG_OBJ_A) += a.obj obj-(CONFIG_OBJ_B) += b.obj
--
Mathematics is the supreme nostalgia of our time.
prev parent reply other threads:[~2005-02-01 4:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-31 7:25 [PATCH 0/8] base-small: CONFIG_BASE_SMALL for small systems Matt Mackall
2005-01-31 7:25 ` [PATCH 1/8] base-small: introduce the CONFIG_BASE_SMALL flag Matt Mackall
2005-01-31 7:25 ` [PATCH 2/8] base-small: shrink major_names hash Matt Mackall
2005-01-31 7:25 ` [PATCH 3/8] base-small: shrink chrdevs hash Matt Mackall
2005-01-31 7:25 ` [PATCH 4/8] base-small: shrink PID tables Matt Mackall
2005-01-31 7:25 ` [PATCH 5/8] base-small: shrink UID hash Matt Mackall
2005-01-31 7:25 ` [PATCH 6/8] base-small: shrink futex queues Matt Mackall
2005-01-31 7:25 ` [PATCH 7/8] base-small: shrink timer hashes Matt Mackall
2005-01-31 7:25 ` [PATCH 8/8] base-small: shrink console buffer Matt Mackall
2005-02-01 0:55 ` [PATCH 0/8] base-small: CONFIG_BASE_SMALL for small systems Horst von Brand
2005-02-01 4:18 ` Matt Mackall [this message]
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=20050201041858.GT2891@waste.org \
--to=mpm@selenic.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vonbrand@inf.utfsm.cl \
/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