public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masoud Sharbiani <masouds@axentra.net>
To: riel@surriel.com
Cc: linux-kernel@vger.kernel.org
Subject: rmap patches for 2.4.30(or 31)
Date: Fri, 03 Jun 2005 15:53:05 -0700	[thread overview]
Message-ID: <42A0DF51.2010809@axentra.net> (raw)

Hello Rik,

It seems that I have successfully hacked 2.4.25 rmap patch so that it 
applies cleanly to 2.4.30 (that is, it compiles, boots and runs great 
under normal conditions); How would I go for testing it and stress 
testing it? It does survive the make -j of kernel (with lots of swap), 
but, when I want to try and run ltp tests, it goes to a bad mood (i.e. 
swapping out massively at first, then a dead silence)

Here is my ltp test run command:
./runltplite.sh -i 1024 -m 128 -p -q -l /tmp/result-rmap -d /home/0tmp/
It ends up forking a lot of loadgen processes that simply allocate 
memory and use it (and CPU), so the system becomes unresponsive; It also 
starts killing processes since it runs out of memory. I don't see any 
hangs or panics, and the system responds to pings and Keyboard dump 
commands, such as right-Alt+Scroll lock and similar ones, and looks it 
is spending most of its time in page_launder() or thereabouts, swap and 
physical memory both become full.
How do you test the rmap patches for correctness before offering them to 
the people out there?
The patch is available from http://masoud.ir/patches/2.4.30-rmap15.patch

Thanks in advance,
Masoud Sharbiani


                 reply	other threads:[~2005-06-03 22:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=42A0DF51.2010809@axentra.net \
    --to=masouds@axentra.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@surriel.com \
    /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