From: Andrea Arcangeli <andrea@e-mind.com>
To: linux@billabong.demon.co.uk, zimerman@deskmail.com,
mauelsha@ez-darmstadt.telekom.de, gerritse@wnet.bos.nl,
dlux@dlux.sch.bme.hu, jalvo@cloud9.net, ebiederm+eric@ccr.net,
steve@netplus.net, "Stephen C. Tweedie" <sct@redhat.com>,
Rik van Riel <H.H.vanRiel@phys.uu.nl>
Cc: linux-kernel@vger.rutgers.edu, linux-mm@kvack.org
Subject: [patch] arca-vm-29, nr_freeable_pages working now
Date: Sun, 24 Jan 1999 19:40:22 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.3.96.990124192824.208A-100000@laser.bogus> (raw)
I have a new VM patch. Unfortunately it's impossible for me to extract it
clean from my tree without waste tons of time. So to try it you'll have to
apply my new whole 2.2.0-pre9_arca-1 patch (that include also some other
new stuff).
ftp://e-mind.com/pub/linux/arca-tree/2.2.0-pre9_arca-1.gz
I am interested about benchmark results and comments if you'll try it. I
am interested also about the low memory feeling. It seems rock solid here
and I had a > x2 improvement against previous code (with 128Mbyte of RAM).
Iteractive feel seems still quite good.
With this patch you'll have a /proc/sys/vm/pager with one number into it.
Such value is the percentage of freeable pages you want during heavy swap.
The most this percentage is high the most your system will run smoother,
but the applications that needs memory will run slower. As default it's
set to 5%.
Andrea Arcangeli
--
To unsubscribe, send a message with 'unsubscribe linux-mm my@address'
in the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
next reply other threads:[~1999-01-24 18:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-24 18:40 Andrea Arcangeli [this message]
1999-02-10 19:00 ` [patch] shrink_mmap from O(num_physpages) to O(nr_lru_pages) Andrea Arcangeli
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=Pine.LNX.3.96.990124192824.208A-100000@laser.bogus \
--to=andrea@e-mind.com \
--cc=H.H.vanRiel@phys.uu.nl \
--cc=dlux@dlux.sch.bme.hu \
--cc=ebiederm+eric@ccr.net \
--cc=gerritse@wnet.bos.nl \
--cc=jalvo@cloud9.net \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=linux@billabong.demon.co.uk \
--cc=mauelsha@ez-darmstadt.telekom.de \
--cc=sct@redhat.com \
--cc=steve@netplus.net \
--cc=zimerman@deskmail.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