From: Jamie Lokier <jamie@shareable.org>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: Mark_H_Johnson@Raytheon.com, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
mfedyk@matchmail.com, m.c.p@wolk-project.de,
owner-linux-mm@kvack.org, plate@gmx.tm
Subject: Re: [PATCH] 2.6.4-rc2-mm1: vm-split-active-lists
Date: Fri, 12 Mar 2004 19:46:01 +0000 [thread overview]
Message-ID: <20040312194601.GE18799@mail.shareable.org> (raw)
In-Reply-To: <4051C8BF.1050001@cyberone.com.au>
Nick Piggin wrote:
> One thing you could do is re read swapped pages when you have
> plenty of free memory and the disks are idle.
Better: re-read swapped pages _and_ file-backed pages that are likely
to be used in future, when you have plenty of free memory and the
disks are idle.
updatedb would push plenty of memory out overnight. But after the
cron jobs and before people wake up in the morning, the kernel would
gradually re-read the pages corresponding to mapped regions in
processes. Possibly with emphasis on some processes more than others.
Possibly remembering some of that likelihood information even when a
particular executable isn't currently running.
During the day, after a big compile the kernel would gradually re-read
pages for processes which are running on your desktop but which you're
not actively using. The editor you were using during the compile will
still be responsive because it wasn't swapped out. The Nautilus or
Mozilla that you weren't using will appear responsive when you switch
to it, because the kernel was re-reading their mapped pages after the
compile, while you didn't notice because you were still using the
editor.
The intention is to avoid those long stalls where you switch to a
Mozilla window and it takes 30 seconds to page in all those libraries
randomly. It's not necessary to keep Mozilla in memory all the time,
even when the memory is specifically useful for a compile, to provide
that illusion of snappy response most of the time.
-- Jamie
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-03-12 19:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-12 14:18 Mark_H_Johnson
2004-03-12 14:27 ` Nick Piggin
2004-03-12 19:46 ` Jamie Lokier [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-12 15:00 Mark_H_Johnson
2004-03-12 15:13 ` Nick Piggin
2004-03-12 19:35 ` Jamie Lokier
2004-03-12 21:17 ` Mike Fedyk
2004-03-12 22:21 ` Jamie Lokier
2004-03-12 22:36 ` Mike Fedyk
2004-03-11 0:04 Nick Piggin
2004-03-11 17:25 ` Marc-Christian Petersen
2004-03-12 9:09 ` Nick Piggin
2004-03-12 9:27 ` Andrew Morton
2004-03-12 9:37 ` Nick Piggin
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=20040312194601.GE18799@mail.shareable.org \
--to=jamie@shareable.org \
--cc=Mark_H_Johnson@Raytheon.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=m.c.p@wolk-project.de \
--cc=mfedyk@matchmail.com \
--cc=owner-linux-mm@kvack.org \
--cc=piggin@cyberone.com.au \
--cc=plate@gmx.tm \
/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