linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: linux-kernel@vger.kernel.org
Cc: jbglaw@lug-owl.de
Subject: Re: Unbloating the kernel, action list
Date: Wed, 15 Oct 2003 06:10:15 -0700	[thread overview]
Message-ID: <20031015131015.GR16158@holomorphy.com> (raw)
In-Reply-To: <20031015124842.GE20846@lug-owl.de>

On Tue, 2003-10-14 15:56:38 -0700, cliff white <cliffw@osdl.org>
>> Marco, if you could supply time on a small client box, and a desired .config,
>> we can add you as a Tinderbox client,
>>  then you have a place to point people when the size increases. 

On Wed, Oct 15, 2003 at 02:48:42PM +0200, Jan-Benedict Glaw wrote:
> I can put on the table:
> 486SLC, 12MB RAM
> i386, 8MB RAM (hey, this box is nearly build up by discrete parts:)
> Am386, 8MB RAM
> P-Classic, 32MB RAM (even that much RAM can go short after an uptme of
> about a month...)
> Unfortunately, you need an additional kernel patch because nearly all
> distros are using mach==i486 which gives you nice sigills on an i386
> otherwise...
> MfG, JBG

Can you quantify the performance impact of cmov emulation (or whatever
it is)? I have a vague notion it could be hard given the daunting task
of switching userspace around to verify it.


-- wli

  reply	other threads:[~2003-10-15 13:07 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-14 11:44 Unbloating the kernel, was: :mem=16MB laptop testing Marco Fioretti
2003-10-14 12:02 ` William Lee Irwin III
2003-10-14 13:24 ` Rik van Riel
2003-10-14 14:30   ` jlnance
2003-10-14 14:54     ` Richard B. Johnson
2003-10-14 16:27     ` Maciej Zenczykowski
2003-10-14 17:33       ` John Bradford
2003-10-14 17:51         ` Richard B. Johnson
2003-10-15 12:43         ` Jan-Benedict Glaw
2003-10-15 13:06           ` William Lee Irwin III
2003-10-15 16:52             ` H. Peter Anvin
2003-10-15 13:08           ` Nick Piggin
2003-10-17 11:50             ` Jan-Benedict Glaw
2003-10-17 23:21               ` Nick Piggin
2003-10-14 18:35       ` tabris
2003-10-14 21:11       ` Roger Larsson
2003-10-15 11:45       ` Jan-Benedict Glaw
2003-10-15 13:06         ` William Lee Irwin III
2003-10-15 13:22           ` Jan-Benedict Glaw
2003-10-24 15:47       ` bill davidsen
2003-10-15  6:06     ` Sandy Harris
2003-10-24 15:59       ` bill davidsen
2003-10-24 16:55         ` M. Fioretti
2003-10-24 17:14           ` bill davidsen
2003-10-25 17:42             ` Geert Uytterhoeven
2003-10-28  9:12           ` Rob Landley
2003-10-14 21:43 ` Unbloating the kernel, action list M. Fioretti
2003-10-14 22:30   ` Martin J. Bligh
2003-10-14 22:56     ` cliff white
2003-10-15 12:48       ` Jan-Benedict Glaw
2003-10-15 13:10         ` William Lee Irwin III [this message]
2003-10-15 15:05           ` Jan-Benedict Glaw
2003-10-19 11:21             ` Adrian Bunk
2003-10-21  8:04               ` Jan-Benedict Glaw
2003-10-15 18:16           ` Gabriel Paubert
2003-10-16  5:19             ` Jan-Benedict Glaw
2003-10-16  8:16               ` Gabriel Paubert
2003-10-16 16:16                 ` Jan-Benedict Glaw
2003-10-17 20:26         ` M. Fioretti
2003-10-17 20:10     ` M. Fioretti

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=20031015131015.GR16158@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=jbglaw@lug-owl.de \
    --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;
as well as URLs for NNTP newsgroup(s).