From: Dan Podeanu <pdan@spiral.extreme.ro>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4 VM & swap question
Date: Sun, 17 Jun 2001 22:12:39 +0300 [thread overview]
Message-ID: <20010617221239.B1027@spiral.extreme.ro> (raw)
In-Reply-To: <20010617104836.B11642@opus.bloom.county>
In-Reply-To: <20010617104836.B11642@opus.bloom.county>; from trini@kernel.crashing.org on Sun, Jun 17, 2001 at 10:48:36AM -0700
On Sun, Jun 17, 2001 at 10:48:36AM -0700, Tom Rini wrote:
> 'lo all. I've got a question about swap and RAM requirements in 2.4. Now,
> when 2.4.0 was kicked out, the fact that you need swap=2xRAM was mentioned.
> But what I'm wondering is what exactly are the limits on this. Right now
> I've got an x86 box w/ 128ram and currently 256swap. When I had 128, I'd get
> low on ram/swap after some time in X, and doing this seems to 'fix' it, in
> 2.4.4. However, I've also got 2 PPC boxes, both with 256:256 in 2.4. One
> of which never has X up, but lots of other activity, and swap usage seems
> to be about the same as 2.2.x (right now 'free' says i'm ~40MB into swap,
> 18day+ uptime). The other box is a laptop and has X up when it's awake and
> that too doesn't seem to have any problem. So what exactly is the real
> minium swap ammount?
I doubt there is a limit. I think 'it depends on what you're planning
to do' is the correct answer. For a blank router, 32mb ram/64 swap can
be enough, for a web/database server, you need more, etc.
next prev parent reply other threads:[~2001-06-17 19:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-17 17:48 Tom Rini
2001-06-17 18:58 ` Jakob Østergaard
2001-06-17 19:06 ` Tom Rini
2001-06-17 21:43 ` alterity
2001-06-17 19:12 ` Dan Podeanu [this message]
2001-06-17 19:20 ` Tom Rini
2001-06-17 19:31 ` Dan Podeanu
2001-06-17 19:33 ` Tom Rini
2001-06-18 11:21 root
2001-06-19 5:30 ` Mike Galbraith
2001-06-19 6:13 ` Rik van Riel
2001-06-19 7:37 ` Mike Galbraith
2001-06-19 7:36 ` Steve Kieu
2001-06-19 8:13 ` Mike Galbraith
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=20010617221239.B1027@spiral.extreme.ro \
--to=pdan@spiral.extreme.ro \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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
all inboxes | Powered by JetHome®