From: Nick Piggin <piggin@cyberone.com.au>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Unbloating the kernel, was: :mem=16MB laptop testing
Date: Wed, 15 Oct 2003 23:08:39 +1000 [thread overview]
Message-ID: <3F8D46D7.1020105@cyberone.com.au> (raw)
In-Reply-To: <20031015124314.GD20846@lug-owl.de>
Jan-Benedict Glaw wrote:
>On Tue, 2003-10-14 18:33:49 +0100, John Bradford <john@grabjohn.com>
>wrote in message <200310141733.h9EHXnYg002262@81-2-122-30.bradfords.org.uk>:
>
>>No, 2.6 should run on a 4MB 386 with no significant performance
>>penalty against 2.0, in my opinion.
>>
>
>Achtually, with HZ at around 100 (or oven 70..80), an old i386 or i486
>will *start* just fine, at least at 8MB. However, over some days /
>weeks, the machine gets slower and slower (my testdrive: my 90MHz
>P-Classic with 16MB). Even with that "much" RAM, I get hit by whatever
>slows down the machine. I *think* that it's the MM subsystem, but I'm
>really not skilled enough with it to blame it:)
>
Thats interesting. Its probably a memory leak I guess. Make sure to rule out
memory leaks in userspace applications, then get /proc/meminfo,
/proc/slabinfo
on the box after it is getting slow, and also, after the box is newly
booted.
Thanks
next prev parent reply other threads:[~2003-10-15 13:08 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 [this message]
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
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=3F8D46D7.1020105@cyberone.com.au \
--to=piggin@cyberone.com.au \
--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 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.