From: Matt Mackall <mpm@selenic.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 1/8] base-small: introduce the CONFIG_BASE_SMALL flag
Date: Mon, 31 Jan 2005 01:25:51 -0600 [thread overview]
Message-ID: <2.687457650@selenic.com> (raw)
In-Reply-To: <1.687457650@selenic.com>
Add CONFIG_BASE_SMALL for miscellaneous core size that don't warrant
their own options. Example users to follow.
Signed-off-by: Matt Mackall <mpm@selenic.com>
Index: mm2/init/Kconfig
===================================================================
--- mm2.orig/init/Kconfig 2005-01-30 21:26:29.000000000 -0800
+++ mm2/init/Kconfig 2005-01-30 21:51:08.000000000 -0800
@@ -286,6 +286,18 @@
reported. KALLSYMS_EXTRA_PASS is only a temporary workaround while
you wait for kallsyms to be fixed.
+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.
+
+config BASE_SMALL
+ int
+ default 0 if BASE_FULL
+ default 1 if !BASE_FULL
+
config FUTEX
bool "Enable futex support" if EMBEDDED
default y
next prev parent reply other threads:[~2005-01-31 7:28 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 ` Matt Mackall [this message]
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
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=2.687457650@selenic.com \
--to=mpm@selenic.com \
--cc=akpm@osdl.org \
--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