From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
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 16:39:11 +0200 [thread overview]
Message-ID: <20030407143911.GI22630@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <3E9188ED.1090109@nortelnetworks.com>
On Mon, 7 April 2003 10:19:25 -0400, Chris Friesen wrote:
>
> 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.
In the scenario above, it costs you a lot. The memory is completely
used, else mozilla wouldn't get swapped out. If you swap it back in
and get rid of fs cache, the next kernel (compile|grep|whatever) will
be slower.
And even in the original scenario, it will be expensive, depending on
your machine. On a notebook, it costs you battery power, which is a
limited resource, *for sure*. You *may* save user time, which *may* be
a limited resource, but not always.
But sure, it is a fun project to hack on, just go ahead and show the
numbers. :)
> 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.
And when it should be done. ;)
Jörn
--
There's nothing better for promoting creativity in a medium than
making an audience feel "Hmm I could do better than that!"
-- Douglas Adams in a slashdot interview
next prev parent reply other threads:[~2003-04-07 14:28 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 [this message]
2003-04-07 18:37 ` Mark Mielke
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=20030407143911.GI22630@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--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®