From: "Benjamin C.R. LaHaise" <blah@kvack.org>
To: Rik van Riel <H.H.vanRiel@phys.uu.nl>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
Andrea Arcangeli <arcangeli@mbox.queen.it>,
Linux MM <linux-mm@kvack.org>,
Linux Kernel <linux-kernel@vger.rutgers.edu>
Subject: Re: cp file /dev/zero <-> cache [was Re: increasing page size]
Date: Tue, 7 Jul 1998 13:32:34 -0400 (8UU\x01) [thread overview]
Message-ID: <Pine.LNX.3.95.980707125719.613B-100000@as200.spellcast.com> (raw)
In-Reply-To: <Pine.LNX.3.96.980707175139.18757A-100000@mirkwood.dummy.home>
On Tue, 7 Jul 1998, Rik van Riel wrote:
> There's a good compromize between balancing per-page
> and per-process. We can simply declare the last X
> (say 8) pages of a process holy unless that process
> has slept for more than Y (say 5) seconds.
This is the wrong fix for the case that Andrea is complaining about -
tossing out chunks of processes piecemeal, resulting in a length page-in
time when the process becomes active again. Two things that might help
with this are: read-ahead on swapins, and *true* swapping. If the system
has run out of ram for the tasks at hand, should it not swap out a process
that's inactive in one fell swoop? Likewise, when said process resumes,
it's probably worth bringing that entire working set back into memory.
That way the user will only experience a brief pause on the first
keystroke issued to bash, not the 'pause on first character type, then
pause as line editing code faults back in...'
-ben
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org
next prev parent reply other threads:[~1998-07-07 17:32 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.3.96.980705072829.17879D-100000@mirkwood.dummy.home>
1998-07-05 11:32 ` Andrea Arcangeli
1998-07-05 17:00 ` Rik van Riel
1998-07-05 18:38 ` Andrea Arcangeli
1998-07-05 19:31 ` Rik van Riel
1998-07-06 10:38 ` Stephen C. Tweedie
1998-07-06 11:42 ` Rik van Riel
1998-07-06 14:20 ` Andrea Arcangeli
1998-07-06 10:31 ` Stephen C. Tweedie
1998-07-06 12:34 ` Andrea Arcangeli
1998-07-06 14:36 ` Stephen C. Tweedie
1998-07-06 19:28 ` Andrea Arcangeli
1998-07-07 12:01 ` Stephen C. Tweedie
1998-07-07 15:54 ` Rik van Riel
1998-07-07 17:32 ` Benjamin C.R. LaHaise [this message]
1998-07-08 13:54 ` Stephen C. Tweedie
1998-07-08 21:19 ` Andrea Arcangeli
1998-07-11 11:18 ` Rik van Riel
1998-07-11 21:11 ` Stephen C. Tweedie
1998-07-08 13:45 ` Stephen C. Tweedie
1998-07-08 18:57 ` Rik van Riel
1998-07-08 22:11 ` Stephen C. Tweedie
1998-07-09 7:43 ` Rik van Riel
1998-07-09 20:39 ` Rik van Riel
1998-07-13 11:54 ` Stephen C. Tweedie
1998-07-05 18:57 ` MOLNAR Ingo
1998-07-06 10:24 ` Stephen C. Tweedie
1998-07-06 13:37 ` Eric W. Biederman
1998-07-07 12:35 ` Stephen C. Tweedie
1998-07-09 13:01 Zachary Amsden
[not found] <199807091442.PAA01020@dax.dcs.ed.ac.uk>
1998-07-09 18:59 ` Rik van Riel
1998-07-09 23:37 ` Stephen C. Tweedie
1998-07-10 5:57 ` Rik van Riel
1998-07-11 14:14 ` Rik van Riel
1998-07-11 21:23 ` Stephen C. Tweedie
1998-07-11 22:25 ` Rik van Riel
1998-07-13 13:23 ` Stephen C. Tweedie
1998-07-12 1:47 ` Benjamin C.R. LaHaise
1998-07-13 13:42 ` Stephen C. Tweedie
1998-07-18 22:10 ` Rik van Riel
1998-07-20 16:04 ` Stephen C. Tweedie
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.95.980707125719.613B-100000@as200.spellcast.com \
--to=blah@kvack.org \
--cc=H.H.vanRiel@phys.uu.nl \
--cc=arcangeli@mbox.queen.it \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=sct@redhat.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