The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Limited RAM - how to save it?
Date: 5 Nov 2001 12:21:51 -0800	[thread overview]
Message-ID: <9s6scv$hq0$1@cesium.transmeta.com> (raw)
In-Reply-To: <20011105125231.A3783@microdata-pos.de>

Followup to:  <20011105125231.A3783@microdata-pos.de>
By author:    Jan-Benedict Glaw <jbglaw@microdata-pos.de>
In newsgroup: linux.dev.kernel
> 
> I'm working on a 4MB linux system (for a customer) which has quite
> limited resources at all:
> 
> 	- 4MB RAM
> 	- 386 or 486 like processor (9..16 BogoMIPS)
> 	- < 100MB HDD
> 	- Quite a lot user space running:-(
> 
> For me, 4MB seems to be a problem. I've stripped diwn the applications
> quite a lot, but 4MB behaves very slow and unresponsible. Adding only
> one more MB solves any performance problem! I've made a small patch
> practically removing printk() from kernel which helps a lot (patch
> attached below). Basically, the running kernel is ~160KB smaller!
> Are there further methods of saving space? I've already done some
> other things, but these don't help that much:
> 

4 MB was the practical minimum for even the very early versions of
Linux.  I would probably suggest backrevving to 2.0 (which is still
maintained) or even 1.2 (which isn't) for a start...

	-hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt	<amsp@zytor.com>

  parent reply	other threads:[~2001-11-05 20:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-05 11:52 Limited RAM - how to save it? Jan-Benedict Glaw
2001-11-05 13:02 ` Matt Bernstein
2001-11-06 10:58   ` szonyi calin
2001-11-06 11:23     ` Matt Bernstein
2001-11-05 20:21 ` H. Peter Anvin [this message]
2001-11-05 22:20   ` Alan Cox
2001-11-05 22:15     ` H. Peter Anvin
2001-11-06  6:58 ` Lars Brinkhoff

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='9s6scv$hq0$1@cesium.transmeta.com' \
    --to=hpa@zytor.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