From: Mark Mielke <mark@mark.mielke.cc>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: Helge Hafting <helgehaf@aitel.hist.no>,
Thomas Schlichter <schlicht@rumms.uni-mannheim.de>,
linux-kernel@vger.kernel.org
Subject: Re: An idea for prefetching swapped memory...
Date: Mon, 7 Apr 2003 14:37:00 -0400 [thread overview]
Message-ID: <20030407183700.GB7311@mark.mielke.cc> (raw)
In-Reply-To: <3E9188ED.1090109@nortelnetworks.com>
On Mon, Apr 07, 2003 at 10:19:25AM -0400, Chris Friesen wrote:
> Helge Hafting wrote:
> >"What we're going to need soon" is the best. It isn't always predictable,
> >but sometimes. "The block following the last we read from some
> >file/fs-structure"
> >is often a good one though.
> With the current setup though, the memory is wasted. It makes sense that
> we should fill the memory up with *something* that is likely to be useful.
>
> If I have mozilla open, start a kernel compile, and then come back half an
> hour later, I would like to see the mozilla pages speculatively loaded back
> into memory.
>
> Since the system is otherwise idle, it doesn't cost anything to do this. I
> think its obvious that it is beneficial to swap in something, the only
> trick is getting a decent heuristic as to what it should be.
Chris: Based on your usage patterns, how would Linux know that you were
going to be opening up Mozilla, and not that you were going to tweak the
kernel source and compile it again?
The only time memory is wasted is when you don't have enough of it, and it
gets trampled for common operations that you perform. All other times, the
memory is loaded, because it was used, which means it might be used again.
mark
--
mark@mielke.cc/markm@ncf.ca/markm@nortelnetworks.com __________________________
. . _ ._ . . .__ . . ._. .__ . . . .__ | Neighbourhood Coder
|\/| |_| |_| |/ |_ |\/| | |_ | |/ |_ |
| | | | | \ | \ |__ . | | .|. |__ |__ | \ |__ | Ottawa, Ontario, Canada
One ring to rule them all, one ring to find them, one ring to bring them all
and in the darkness bind them...
http://mark.mielke.cc/
next prev parent reply other threads:[~2003-04-07 18:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-07 8:26 Thomas Schlichter
2003-04-07 10:21 ` Con Kolivas
2003-04-07 10:47 ` Thomas Schlichter
2003-04-07 11:24 ` Måns Rullgård
2003-04-07 12:46 ` Thomas Schlichter
2003-04-07 18:33 ` Mark Mielke
2003-04-07 13:24 ` Helge Hafting
2003-04-07 14:19 ` Chris Friesen
2003-04-07 14:39 ` Jörn Engel
2003-04-07 18:37 ` Mark Mielke [this message]
2003-04-07 18:49 ` Chris Friesen
2003-04-07 19:35 ` Mark Mielke
2003-04-07 19:39 ` Robert White
2003-04-07 20:44 ` Chris Friesen
2003-04-07 11:36 ` Christophe Saout
2003-04-07 11:48 ` Måns Rullgård
2003-04-07 12:19 ` Jörn Engel
2003-04-07 12:45 ` Christophe Saout
2003-04-07 16:30 ` Magnus Danielson
2003-04-07 12:32 ` David Zaffiro
2003-04-07 12:43 ` Jörn Engel
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=20030407183700.GB7311@mark.mielke.cc \
--to=mark@mark.mielke.cc \
--cc=cfriesen@nortelnetworks.com \
--cc=helgehaf@aitel.hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=schlicht@rumms.uni-mannheim.de \
/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
all inboxes | Powered by JetHome®