public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Tuijnman <daniel@ATComputing.nl>
To: "M. Edward (Ed) Borasky" <znmeb@aracnet.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Memory management problems in 2.4.16
Date: Wed, 9 Jan 2002 23:47:06 +0100	[thread overview]
Message-ID: <20020109234706.B4555@ATComputing.nl> (raw)
In-Reply-To: <20020109143434.A20955@ATComputing.nl> <Pine.LNX.4.33.0201090640080.13260-100000@shell1.aracnet.com>
In-Reply-To: <Pine.LNX.4.33.0201090640080.13260-100000@shell1.aracnet.com>; from znmeb@aracnet.com on Wed, Jan 09, 2002 at 06:47:57AM -0800

> > I installed a 2.4.16 kernel on a 486DX2-50 machine with 8MB memory and
> > 24MB swap and got insurmountable problems.
> 
> [snip]
> 
> > It seems to me that something definitely is wrong with the kernel's
> > memory management.
> 
> Well ... maybe *in theory* 2.4.16 should work on a machine with that
> little RAM but I'd say in practice Linux has simply outgrown your
> machine. Have you tried any other 2.4 kernels, say, before 2.4.10 when
> the VM changed?

No I haven't. Was the older VM better, then? Sorry to put it so blunt,
but if it can't swap out unneeded data, it is broken.
I've seen here people report having 1GB of memory and still running out
of it...

> Have you considered going to a garage sale and spending
> the local equivalent of $25 or $30 US for a more powerful computer?

1. I'm setting up this machine to act as a firewall for my cable
connection, so why do I need a more powerful computer?

2. My first Linux experience was on a P60 with 8MB of memory, 16MB swap.
I ran X and used TeX on my 300p. Ph.D. thesis, and that ran fine.
So why should I need more to get less?

I happen to have this machine, it works and is suited for the job.
Now please let's not get a bloatware, consumerism-throw away attitude.

Before this starts a flameware, let me make one thing clear: my main
point is, there is something wrong when an application, for which there
is plenty of (virtual) memory, grinds the whole machine to a standstill.

Greetings,
Daniel Tuijnman


  reply	other threads:[~2002-01-09 22:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-09 13:34 Memory management problems in 2.4.16 Daniel Tuijnman
2002-01-09 13:39 ` Roy Sigurd Karlsbakk
2002-01-09 14:47 ` M. Edward (Ed) Borasky
2002-01-09 22:47   ` Daniel Tuijnman [this message]
2002-01-09 22:57     ` Rik van Riel
2002-01-11  0:26       ` Daniel Tuijnman
2002-01-10 22:40   ` Pavel Machek
2002-01-11  3:42     ` Rik van Riel
2002-01-11  4:46       ` Dan Chen
2002-01-11  5:01         ` William Lee Irwin III

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=20020109234706.B4555@ATComputing.nl \
    --to=daniel@atcomputing.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=znmeb@aracnet.com \
    /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