From: "Luiz Fernando N. Capitulino" <lcapitulino@mandriva.com.br>
To: hamid.jahanjou@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] VM: Implements the swap-out page-clustering technique
Date: Wed, 24 Sep 2008 10:56:57 -0300 [thread overview]
Message-ID: <20080924105657.78265a63@doriath.conectiva> (raw)
In-Reply-To: <48BFCECE.90103@gmail.com>
Em Thu, 04 Sep 2008 15:34:30 +0330
"Hamid R. Jahanjou" <hamid.jahanjou@gmail.com> escreveu:
| From: Hamid R. Jahanjou
|
| Implements the idea of swap-out page clustering from *BSD for
| Linux. Each time a candidate page is to be swapped out,
| virtually-nearby pages are scanned to find eligible pages to be
| swapped out too as a cluster. This technique increases the likelihood of
| bringing in related data on a page fault and decreases swap space
| fragmentation in the long run. Currently, Linux searches only
| physically-nearby pages which is not optimal since, over time, physically-
| adjacent pages may become unrelated.
|
| The code can be statically tuned. No benchmarks. I'm not sure whether
| the added complexity is acceptable.
Sorry for this (very) late response, but I ran some very simple tests
this week and thought you might be interested in the results.
The test machine has 512MB of RAM. For the tests I booted with 64MB
and setup a 512MB swap file.
For the first test I let an allyesconfig kernel building for several
hours with six jobs (make -j6). I did not have any problems, so
considering that your code was used I think it is stable enough.
In the second test I have built an allnoconfig kernel with and without
your patches, still with six jobs. Results:
2.6.27-rc7-vanilla 44:12 minutes
2.6.27-rc7-pgc 52:09 minutes
(pgc means page-clustering patches).
For both builds I did not change any swap paramenter and I could
observe that about 80MB of swap were used most of the time.
But please, note that these tests were quite far from being 'scientific'
eg. I should have built the kernel more times and should have tried other
setups...
I will wait for the next version of the patches to run more serious
tests.
--
Luiz Fernando N. Capitulino
prev parent reply other threads:[~2008-09-24 13:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-04 12:04 Hamid R. Jahanjou
2008-09-04 23:14 ` Rik van Riel
2008-09-04 23:14 ` Andrew Morton
2008-09-05 7:45 ` Hamid R. Jahanjou
2008-09-05 6:58 ` Andrew Morton
2008-09-05 9:19 ` Andi Kleen
2008-09-05 20:27 ` Hamid R. Jahanjou
2008-09-05 19:45 ` Andi Kleen
2008-09-06 5:42 ` Rik van Riel
2008-09-08 0:28 ` Zan Lynx
2008-09-08 0:55 ` Rik van Riel
2008-09-10 8:16 ` Hamid R. Jahanjou
2008-09-10 17:08 ` Ray Lee
2008-09-10 17:39 ` Rik van Riel
2008-09-08 3:50 ` Li Yu
2008-09-08 9:51 ` hamidreza jahanjou
[not found] ` <48C4FECF.2000708@gmail.com>
2008-09-08 10:31 ` Li Yu
2008-09-24 13:56 ` Luiz Fernando N. Capitulino [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=20080924105657.78265a63@doriath.conectiva \
--to=lcapitulino@mandriva.com.br \
--cc=hamid.jahanjou@gmail.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
all inboxes | Powered by JetHome®