linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <H.H.vanRiel@fys.ruu.nl>
To: linux-kernel <linux-kernel@vger.rutgers.edu>
Cc: linux-mm <linux-mm@kvack.org>
Subject: vhand-2.1.64... problems solved
Date: Tue, 18 Nov 1997 11:47:26 +0100 (MET)	[thread overview]
Message-ID: <Pine.LNX.3.91.971118113503.416A-100000@mirkwood.dummy.home> (raw)

Hi there,

I've found the cause for vhand eating too much memory. Well, I think
I have... I think it is because kswapd would wake up vhand after 3
failures, while vhand would guarantee that 1/32nd of memory is ready
to swap out... Now, putting KSWAPD_MAX_FAIL at 128 (!) has alleviated
this problem, it's not over yet, but at least it's not severe.
(at the moment I'm looking at an uncharged kswapd and 5% max for
vhand. probably vhand gets billed for kswapd :-)
... somebody with an Alpha (HZ=1024) should take a closer look at 
this...

I also merged my patch with the excellent network_atomic_alloc_59
patch from Zlato Calusic <Zlato.Calusic@CARNet.hr>. Thanks Zlato!

-------------
Vhand is a patch that improves system responsiveness when memory
is short. It does this by also aging shared memory and buffers.
It also applies a fairer aging sceme to the aging of normal
program pages.
Although this patch is reported to be rock-solid, I still consider
it Beta. This is mainly because I've only had about 15 success
stories in my mailbox (and no failures:-).

You can find the patch on linux-mama <http://www.huwig.de/linux/mama/>
and on my home page <http://www.fys.ruu.nl/~riel/>.
-------------

Please send success-stories, bug-reports, bugfixes and flames
to me. Anything will help...

Rik.

----------
Send Linux memory-management wishes to me: I'm currently looking
for something to hack...

                 reply	other threads:[~1997-11-18 12:15 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=Pine.LNX.3.91.971118113503.416A-100000@mirkwood.dummy.home \
    --to=h.h.vanriel@fys.ruu.nl \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=linux-mm@kvack.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