From: Matt Mackall <mpm@selenic.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH 1/8] core-small: Add option to embedded menu
Date: Fri, 21 Jan 2005 18:09:48 -0600 [thread overview]
Message-ID: <2.464233479@selenic.com> (raw)
In-Reply-To: <1.464233479@selenic.com>
Add CONFIG_CORE_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: tiny/init/Kconfig
===================================================================
--- tiny.orig/init/Kconfig 2004-12-04 15:42:40.394703286 -0800
+++ tiny/init/Kconfig 2004-12-04 19:24:36.404346070 -0800
@@ -287,6 +287,12 @@
reported. KALLSYMS_EXTRA_PASS is only a temporary workaround while
you wait for kallsyms to be fixed.
+config CORE_SMALL
+ default n
+ bool "Enable various size reductions for core" if EMBEDDED
+ help
+ This reduces the size of miscellaneous core kernel data structures.
+
config FUTEX
bool "Enable futex support" if EMBEDDED
default y
next prev parent reply other threads:[~2005-01-22 0:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-22 0:09 [PATCH 0/8] core-small: Introduce CONFIG_CORE_SMALL from -tiny Matt Mackall
2005-01-22 0:09 ` Matt Mackall [this message]
2005-01-22 0:09 ` [PATCH 2/8] core-small: Collapse major names hash Matt Mackall
2005-01-22 0:09 ` [PATCH 3/8] core-small: Collapse chrdevs hash Matt Mackall
2005-01-22 0:09 ` [PATCH 4/8] core-small: Shrink PID lookup tables Matt Mackall
2005-01-22 0:09 ` [PATCH 5/8] core-small: Shrink uid hash Matt Mackall
2005-01-22 0:09 ` [PATCH 6/8] core-small: Shrink futex queue hash Matt Mackall
2005-01-22 0:09 ` [PATCH 7/8] core-small: Shrink timer lists Matt Mackall
2005-01-22 0:09 ` [PATCH 8/8] core-small: Shrink console buffer Matt Mackall
2005-01-23 8:40 ` [PATCH 0/8] core-small: Introduce CONFIG_CORE_SMALL from -tiny Andrew Morton
2005-01-23 17:52 ` Matt Mackall
2005-01-23 21:05 ` Andrew Morton
2005-01-24 2:50 ` Matt Mackall
2005-01-24 20:00 ` Alan Cox
2005-01-24 22:47 ` Tim Bird
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.464233479@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.