From: "Jacek Popławski" <jpopl@interia.pl>
To: linux-kernel@vger.kernel.org
Subject: Re: Bad, bad, bad VM behaviour in 2.4.10
Date: Wed, 26 Sep 2001 10:05:02 +0200 [thread overview]
Message-ID: <20010926100502.A2824@localhost.localdomain> (raw)
In-Reply-To: <3BB0F483.69929A79@ditec.um.es> <Pine.LNX.4.21.0109251702240.2193-100000@freak.distro.conectiva>
In-Reply-To: <Pine.LNX.4.21.0109251702240.2193-100000@freak.distro.conectiva>; from marcelo@conectiva.com.br on Tue, Sep 25, 2001 at 05:03:35PM -0300
On Tue, Sep 25, 2001 at 05:03:35PM -0300, Marcelo Tosatti wrote:
> I need some information which may help confirm a guess of mine:
>
> Do you have swap available ?
>
> If so, there was available anonymous memory to be swapped out ?
As I wrote before - on my system this problem appear even when swap is on, and
there is enough swap, but not enought RAM (i.e. when system just starts using
swap...).
next prev parent reply other threads:[~2001-09-26 8:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-25 21:17 Bad, bad, bad VM behaviour in 2.4.10 Juan
2001-09-25 20:03 ` Marcelo Tosatti
2001-09-25 21:52 ` khromy
2001-09-25 22:08 ` Juan
2001-09-25 21:23 ` Marcelo Tosatti
2001-09-26 10:36 ` Juan
2001-09-26 8:05 ` Jacek Popławski [this message]
2001-09-26 15:23 ` Dan Mann
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=20010926100502.A2824@localhost.localdomain \
--to=jpopl@interia.pl \
--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