From: Andrzej Krzysztofowicz <kufel!ankry@green.mif.pg.gda.pl>
To: kufel!conectiva.com.br!riel@green.mif.pg.gda.pl (Rik van Riel)
Cc: kufel!able.es!jamagallon@green.mif.pg.gda.pl (J . A . Magallon),
kufel!vger.kernel.org!linux-kernel@green.mif.pg.gda.pl (Linux
Kernel)
Subject: Re: vm in 2.4.5
Date: Sat, 26 May 2001 22:23:14 +0200 (CEST) [thread overview]
Message-ID: <200105262023.WAA02740@kufel.dom> (raw)
In-Reply-To: <Pine.LNX.4.21.0105261049130.30264-100000@imladris.rielhome.conectiva> from "Rik van Riel" at maj 26, 2001 10:54:16
> On Sat, 26 May 2001, J . A . Magallon wrote:
> > It does not begin to use swap in a growing fashion, it just appears
> > full in a moment.
>
> It gets _allocated_ in a moment, but things don't actually get
> swapped out. This isn't a problem.
>
> The real problem is that we don't actively reclaim swap space
> when it gets full. We just assign swap to parts of processes,
> but we never reclaim it when we need swap space for something
> else; at least, not until the process exit()s or exec()s.
As I understand the original message, before the compilation and after the
system is in a "similar" state ("the same" processes should be running; even
less of them if some were killed by OOM).
: total used free shared buffers cached
: -/+ buffers/cache: 49908 205780
: Swap: 152576 0 152576
~49 MB in use befere the test,
: -/+ buffers/cache: 14844 240844
: Swap: 152576 152576 0
~149 MB allocated swap. By processes of total size of 49 MB ? Strange...
Either the test shows some leak in running userspace processes (they
allocate a lot of memory) as an effect of memory shortage (strange) or there
is some leak in the kernel. Or the test is bad (something else is running
when it finishes).
Am I right ?
Andrzej
next prev parent reply other threads:[~2001-05-27 0:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-26 8:25 vm in 2.4.5 J . A . Magallon
2001-05-26 13:54 ` Rik van Riel
2001-05-26 20:23 ` Andrzej Krzysztofowicz [this message]
2001-05-27 23:59 ` J . A . Magallon
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=200105262023.WAA02740@kufel.dom \
--to=kufel!ankry@green.mif.pg.gda.pl \
--cc=kufel!able.es!jamagallon@green.mif.pg.gda.pl \
--cc=kufel!conectiva.com.br!riel@green.mif.pg.gda.pl \
--cc=kufel!vger.kernel.org!linux-kernel@green.mif.pg.gda.pl \
/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