From: Matt Mackall <mpm@selenic.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/8] core-small: Introduce CONFIG_CORE_SMALL from -tiny
Date: Fri, 21 Jan 2005 18:09:47 -0600 [thread overview]
Message-ID: <1.464233479@selenic.com> (raw)
This set of patches introduces a new config option CONFIG_CORE_SMALL
from the -tiny tree for small systems. This series should apply
cleanly against 2.6.11-rc1-mm2.
When selected, it enables various tweaks to miscellaneous core data
structures to shrink their size on small systems. While each tweak is
fairly small, in aggregate they can save a substantial amount of
memory.
1 Add option to embedded menu
2 Collapse major names hash
3 Collapse chrdevs hash
4 Shrink PID lookup tables
5 Shrink uid hash
6 Shrink futex queue hash
7 Shrink timer lists
8 Shrink console buffer
next 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 Matt Mackall [this message]
2005-01-22 0:09 ` [PATCH 1/8] core-small: Add option to embedded menu Matt Mackall
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=1.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.