All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gabriel Paubert <paubert@iram.es>
To: linux-kernel@vger.kernel.org
Subject: Re: Unbloating the kernel, action list
Date: Thu, 16 Oct 2003 10:16:11 +0200	[thread overview]
Message-ID: <20031016081611.GA14949@iram.es> (raw)
In-Reply-To: <20031016051951.GP20846@lug-owl.de>

On Thu, Oct 16, 2003 at 07:19:51AM +0200, Jan-Benedict Glaw wrote:
> On Wed, 2003-10-15 20:16:58 +0200, Gabriel Paubert <paubert@iram.es>
> wrote in message <20031015181658.GA9652@iram.es>:
> > On Wed, Oct 15, 2003 at 06:10:15AM -0700, William Lee Irwin III wrote:
> > > On Tue, 2003-10-14 15:56:38 -0700, cliff white <cliffw@osdl.org>
> > > 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.
> > The other problem of the 386 is that it has a fundamental MMU flaw:
> > no write protection on kernel mode accesses to user space, which makes 
> > put_user() intrinsically racy on a 386 and way more bloated when it is
> > inlined (access_ok has to call a function which searches the VMA tree).
> 
> However, this problem exists since the very first hour. Linux once
> really ran quite well on those machines...

Yes, but VM sharing between threads was rather infrequent back then
and you need shared VM to create the race.

> 
> I've rebooted my P-Classic router last night. Maybe I can see (in two
> weeks or in a month or the like...) why it slows down, even with 32MB
> RAM...

It might be related to the size-4096 memory leak others are reporting 
right now. I don't know, but it's not such a far-fetched hypothesis
either.

	Gabriel

  reply	other threads:[~2003-10-16  8:24 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
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 [this message]
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=20031016081611.GA14949@iram.es \
    --to=paubert@iram.es \
    --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.