From: Moshe Zadka <moshez@math.huji.ac.il>
To: linux-mm@kvack.org
Subject: Re: ideas for a swapping daemon
Date: Thu, 18 Dec 1997 20:53:28 +0200 (IST) [thread overview]
Message-ID: <Pine.LNX.3.96.971218205013.1610B-100000@ladybug.org.il> (raw)
In-Reply-To: <Pine.LNX.3.95.971218112022.10225C-100000@as200.spellcast.com>
Seems like a good idea. But experience with vhand
shows that what we should be most careful about is
waking the swapping daemon too often, consuming
resources. So, if anyone is writing it (I might
start by patching kswapd's routines to allow
"forcing"), please keep an easily configurable
parameter (perhaps run-time adjusted through proc-fs)
controlling how often it is woken up, for easier
determining of the heuristics.
--
Moshe Zadka - moshez@math.huji.ac.il
Violating RFC2049 Should Be a Shooting Offense
next prev parent reply other threads:[~1997-12-19 8:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-18 16:21 Benjamin LaHaise
1997-12-18 18:53 ` Moshe Zadka [this message]
1997-12-19 11:24 ` Rik van Riel
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.971218205013.1610B-100000@ladybug.org.il \
--to=moshez@math.huji.ac.il \
--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