From: Matt Mackall <mpm@selenic.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: 2.6.2-rc3-tiny1 for small systems
Date: Sat, 31 Jan 2004 23:23:48 -0600 [thread overview]
Message-ID: <20040201052348.GW21888@waste.org> (raw)
This is the latest release of the -tiny kernel tree. 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. Target users
are things like embedded systems, small or legacy desktop folks, and
handhelds.
Latest release includes:
- update to 2.6.2-rc3
- add latest netdrvr patchkit (Jeff Garzik)
- numerous compile warning fixes from last release
- work for compiling with gcc 3.4
- smaller, cleaned up inflate code for kernel, initramfs, etc.
- optional support for file locking
- optional support for uid16 interfaces
- enhanced CPU feature selection (Adrian Bunk)
- selectable vendor support for MTRRs
- optional TSC timer support
- optional ramfs-based shmem/tmpfs support
- minor space-saving cleanups
As always, I'm looking for more ideas for space-savings. Suggestions
in the TCP/IP area are especially useful right now.
Here's a test boot of my development config (console, ide, ext2, and
ipv4) with mem=2m, which is actually only 1664k after accounting for
BIOS memory holes:
Uncompressing Linux... Ok, booting the kernel.
# mount /proc
# cat /proc/meminfo
MemTotal: 980 kB [up from 916k for last release!]
MemFree: 312 kB
Buffers: 32 kB
Cached: 296 kB
SwapCached: 0 kB
Active: 400 kB
Inactive: 48 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 980 kB
LowFree: 312 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 0 kB
Writeback: 0 kB
Mapped: 380 kB
Slab: 0 kB
Committed_AS: 132 kB
PageTables: 24 kB
VmallocTotal: 1032172 kB
VmallocUsed: 0 kB
VmallocChunk: 1032172 kB
#
The patch can be found at:
http://selenic.com/tiny/2.6.2-rc3-tiny1.patch.bz2
http://selenic.com/tiny/2.6.2-rc3-tiny1-broken-out.tar.bz2
Webpage for your bookmarking pleasure:
http://selenic.com/tiny-about/
--
Matt Mackall : http://www.selenic.com : Linux development and consulting
next reply other threads:[~2004-02-01 5:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-01 5:23 Matt Mackall [this message]
2004-02-02 18:39 ` 2.6.2-rc3-tiny1 for small systems Adrian Bunk
2004-02-02 19:29 ` Matt Mackall
2004-02-02 20:50 ` Adrian Bunk
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=20040201052348.GW21888@waste.org \
--to=mpm@selenic.com \
--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