From: Con Kolivas <kernel@kolivas.org>
To: Thomas Schlichter <schlicht@uni-mannheim.de>,
linux-kernel@vger.kernel.org
Subject: Re: An idea for prefetching swapped memory...
Date: Mon, 7 Apr 2003 20:21:16 +1000 [thread overview]
Message-ID: <200304072021.17080.kernel@kolivas.org> (raw)
In-Reply-To: <200304071026.47557.schlicht@uni-mannheim.de>
On Mon, 7 Apr 2003 18:26, Thomas Schlichter wrote:
> Hello,
>
> some days ago some friends and me argued about a feature which seems not to
> be included in current OSs but could improve useability mainly for desktop
> computers.
>
> 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)
>
> One is surfing the internet and having some browser windows opened. Now,
> without closing the browser windows, he is playing some game which needs
> pretty much memory so the browsers memory is getting swapped out. After
> finishing gaming he's going to make some coffee and then surfing the
> internet again.
> But even if the computer was IDLE for a time and, as the game was closed
> again, some memory is really FREE, the pages for the browser are swapped in
> just when they are needed and not in advance.
>
> With this feature there should be no performance decrease because only free
> resources would be used, and if pages were swapped in but not be used, they
> stay not dirty and so have not to be written to disk when they are swapped
> out again. But the improvements should be obvious if simply the last swaped
> out pages are swapped in again...
This has been argued before. Why would the last swapped out pages be the best
to swap in? The vm subsystem has (somehow) decided they're the least likely
to be used again so why swap them in? Alternatively how would it know which
to swap in instead?
Con
next prev parent reply other threads:[~2003-04-07 10:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-07 8:26 An idea for prefetching swapped memory Thomas Schlichter
2003-04-07 10:21 ` Con Kolivas [this message]
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
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=200304072021.17080.kernel@kolivas.org \
--to=kernel@kolivas.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.