From: Tom Rini <trini@kernel.crashing.org>
To: Jakob ?stergaard <jakob@unthought.net>, linux-kernel@vger.kernel.org
Subject: Re: 2.4 VM & swap question
Date: Sun, 17 Jun 2001 12:06:45 -0700 [thread overview]
Message-ID: <20010617120645.E11642@opus.bloom.county> (raw)
In-Reply-To: <20010617104836.B11642@opus.bloom.county> <20010617205835.A12767@unthought.net>
In-Reply-To: <20010617205835.A12767@unthought.net>
On Sun, Jun 17, 2001 at 08:58:35PM +0200, Jakob ?stergaard wrote:
> 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?
>
> It completely totally and absolutely depends on the kind of workloads you put
> your system under.
Well, yes. :) But 2.4.x is much more swap-happy then 2.2.x was. I haven't
changed my workload that much but the 256 swap became noticiably needed
recently.
> There is no simple answer. swap = 2*phys may be reasonable for some desktop
> uses, I don't know. But there *is* *no* *simple* *answer*.
Yes. The problem is the requirement has seemingly doubled recently.
> With the amount of work that's gone into just *understanding* why the VM
> behaves as it does (even after the VM rewrite that was done exactly in order to
> come up with a VM we could *understand*), it's beyond me how anyone can even
> begin to think that one can define a set of simple and exact rules for minimum
> or "optimal" (whatever that means) values for swap.
Well, it's also been said that the 'need' for 2xswap was fixed by one of the
probably-not-yet-in-linus'-tree VM patches. And that it's 'artificial'
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2001-06-17 19:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-17 17:48 2.4 VM & swap question Tom Rini
2001-06-17 18:58 ` Jakob Østergaard
2001-06-17 19:06 ` Tom Rini [this message]
2001-06-17 21:43 ` alterity
2001-06-17 19:12 ` Dan Podeanu
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=20010617120645.E11642@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=jakob@unthought.net \
--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;
as well as URLs for NNTP newsgroup(s).