public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Matt Mackall <mpm@selenic.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] -tiny tree for small systems (2.6.0-test11)
Date: Fri, 12 Dec 2003 08:44:43 -0700	[thread overview]
Message-ID: <20031212154443.GN23731@stop.crashing.org> (raw)
In-Reply-To: <20031212033734.GG23787@waste.org>

On Thu, Dec 11, 2003 at 09:37:34PM -0600, Matt Mackall wrote:

> This is the first release of a new kernel tree dubbed '-tiny' (someone
> already took -mm). The aim of this tree is to collect patches that
> reduce kernel disk and memory footprint as well as tools for working
> on small systems, an area Linux mainstream has been moving away from
> since Linus got a real job. Target users are things like embedded
> systems, small or legacy desktop folks, and handhelds.
> 
> To get the ball rolling, I've thrown in about 50 patches that trim
> various bits of the kernel, almost all configurable, and a fair number
> may eventually be appropriate for mainline. All the config options are
> currently thrown under CONFIG_EMBEDDED and many of the minor tweaks
> are covered under a set of config options called CONFIG_CORE_SMALL,
> CONFIG_NET_SMALL, and CONFIG_CONSOLE_SMALL.
> 
> Nifty things I've included:
>  - building with -Os
>  - 4k process stacks (via -wli)
>  - configurable removal of printk, BUG, and panic() strings
>  - configurable HZ
>  - configurable support for vm86, core dumps, kcore, sysfs, aio, etc.
>  - a very nice kmalloc auditing system via /proc/kmalloc
>  - auditing of bootmem usage
>  - a system for counting inline instantiations
>  - my netpoll/netconsole patches
>  - my drivers/char/random fixups

I'd like to suggest you check out the "tweaks" idea I tossed out here:
http://www.ussg.iu.edu/hypermail/linux/kernel/0211.0/2229.html
If this sounds interesting, I've got a version of the patch (albeit old
and not applying directly right now I bet) that moved things into header
files and got all of the dependancy stuff correct except for the initial
run (so I think I was forcing an update with any make invocation, but
there were no spurious recompiles).

-- 
Tom Rini
http://gate.crashing.org/~trini/

  parent reply	other threads:[~2003-12-12 15:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-12  3:37 [ANNOUNCE] -tiny tree for small systems (2.6.0-test11) Matt Mackall
2003-12-12  4:09 ` William Lee Irwin III
2003-12-12 15:44 ` Tom Rini [this message]
2003-12-12 15:59   ` Matt Mackall
2003-12-12 16:05     ` Tom Rini
2003-12-12 16:17       ` bill davidsen
2003-12-12 16:51         ` Tom Rini

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=20031212154443.GN23731@stop.crashing.org \
    --to=trini@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.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