From: David Zaffiro <davzaffiro@netscape.net>
To: Thomas Schlichter <schlicht@uni-mannheim.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: An idea for prefetching swapped memory...
Date: Mon, 07 Apr 2003 14:32:26 +0200 [thread overview]
Message-ID: <3E916FDA.8070809@netscape.net> (raw)
In-Reply-To: <200304071026.47557.schlicht@uni-mannheim.de>
> The idea was about prefetching swapped out pages when some memory is free, the
> CPU is idle and the I/O load is low.
>
> So this should not 'cost' much but behave better on following situation:
> (I think there are even more such situations, this one should just be an
> example)
Wouldn't it cost almost twice as much when the user requests a different task, instead of the just
swaped-in "last swaped-out task(s)"?!
Instead of loading this directly into a free portion of phys. memory, the
just-swapped-in-ex-swapped-out task(s) would need to be swapped-out *again* in favour of the
to-be-swaped-in task...
Or am I wrong here?
next prev parent reply other threads:[~2003-04-07 12:21 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
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 [this message]
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=3E916FDA.8070809@netscape.net \
--to=davzaffiro@netscape.net \
--cc=linux-kernel@vger.kernel.org \
--cc=schlicht@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®