public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vasco Figueira <figueira@europe.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] reclaim dirty dead swapcache pages
Date: Thu, 31 May 2001 20:31:18 +0100	[thread overview]
Message-ID: <3B169C06.1010507@europe.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0105301729080.5231-100000@freak.distro.conectiva> <3B168B59.70906@europe.com>

Hi again,

Vasco Figueira wrote:

 >I've opened x, gnome, mozilla, mozilla -mail, 3 gnome-terminals, pan, 
 >xmms, some files and javac. Swap was totally filled up and it didn't 
 >froze (good!). However suddently it came very busy (i thougth it was 
 >going to freeze again), the music stopped, and came back to normal 
 >again. It had killed xmms, I noticed after.

 >Is it intentional to kill processes? Well, it does reolve the problem, 
 >but kills some processes, probably the most eager ones. I will keep 
 >using this patch and report again if something relevant is found.

 >So far, so good, this is better tha having to swapoff & swapon all the 
 >time. Nice work Marcelo.

Continuing the saga of testing this patch, some more things:

* Swap gets *really* filled up. I don't remember having swap totally 
filled with 2.2. and this has 20M more (doesn't have to do with this 
patch, I think)

* kernel appears to try to free pages only when they are desperatly 
needed, i.e., when swap is full and a big process is needing mem. As an 
example, i was calm editing some text files (swap was full), and called 
javac. System went down to his knees, music stopped, mouse had repent 
stops and javac outputed:"Killed". I assume it was killed :-)

javac was called again and then ran more smootly. Perhaps because his 
pages were already there, no?

It may be better to try to free pages before we get into heavy load. If 
not, we get a pseudo-freeze and a killed process. Wich is not... wonderful.

Comments?
-- 
Regards,
                             Vasco Figueira

http://students.fct.unl.pt/users/vaf12086/


      reply	other threads:[~2001-05-31 19:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-30 17:51 [PATCH] reclaim dirty dead swapcache pages Marcelo Tosatti
2001-05-30 20:32 ` Marcelo Tosatti
2001-05-30 22:15   ` J . A . Magallon
2001-05-30 20:48     ` Marcelo Tosatti
2001-05-31 18:20   ` Vasco Figueira
2001-05-31 19:31     ` Vasco Figueira [this message]

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=3B169C06.1010507@europe.com \
    --to=figueira@europe.com \
    --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