linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Billy Harvey <Billy.Harvey@thrillseeker.net>
To: Rik van Riel <H.H.vanRiel@phys.uu.nl>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
	Linux MM <linux-mm@kvack.org>,
	Linux Kernel <linux-kernel@vger.rutgers.edu>
Subject: Re: [PATCH] swapin readahead and fixes
Date: Mon, 07 Dec 1998 21:51:51 -0500	[thread overview]
Message-ID: <366C9447.2B4E9693@thrillseeker.net> (raw)
In-Reply-To: <Pine.LNX.3.96.981208032438.8407C-100000@mirkwood.dummy.home>

Rik van Riel wrote:
> 
> On Mon, 7 Dec 1998, Billy Harvey wrote:
> 
> > Has anyone ever looked at the following concept?  In addition to a
> > swap-in read-ahead, have a swap-out write-ahead.  The idea is to use
> > all the avaialble swap space as a mirror of memory.
> 
> We do something a bit like this in 2.1.130+. Writing out all
> pages to swap will use far too much I/O bandwidth though, so
> we will never do that...
> 
Rik,

That's my point though about not taking I/O time away from other tasks. 
Only mirror pages to swap if there's nothing else blocked for I/O - put
any free time to work, and mirror pages if swap memory allows in
anticipation that it may be swapped out later.  I suppose a
least-recently-used approach on the pages would have the highest
payback.  I realize the CPU may be used a little more, but other than
rc5des it's idle a good bit of the time anyway - perhaps this could be
one step above an idle task.

Billy
-- 
Billy.Harvey@thrillseeker.net
--
This is a majordomo managed list.  To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org

  reply	other threads:[~1998-12-08  2:52 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-03 17:56 Rik van Riel
1998-12-04 11:34 ` Stephen C. Tweedie
1998-12-04 14:02   ` Rik van Riel
1998-12-04 14:34     ` Stephen C. Tweedie
1998-12-05  9:46       ` Gerard Roudier
1998-12-07 16:50         ` Stephen C. Tweedie
1998-12-08  1:34           ` Billy Harvey
1998-12-08  2:31             ` Rik van Riel
1998-12-08  2:51               ` Billy Harvey [this message]
1998-12-08  3:00                 ` Rik van Riel
1998-12-08 12:35               ` Stephen C. Tweedie
1998-12-08 13:51                 ` Rik van Riel
1998-12-09  2:41               ` Drago Goricanec
1998-12-09 11:58                 ` Stephen C. Tweedie
1998-12-08 12:21             ` Stephen C. Tweedie
1998-12-05 10:47       ` Gerard Roudier
1998-12-04 19:25 ` Chris Evans
1998-12-04 20:47   ` Rik van Riel
1998-12-05 18:59     ` Alan Cox
1998-12-05 19:02       ` Rik van Riel
1998-12-06  5:20       ` Rik van Riel
1998-12-06  5:23       ` Steve VanDevender
1998-12-07 11:52   ` Rik van Riel

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=366C9447.2B4E9693@thrillseeker.net \
    --to=billy.harvey@thrillseeker.net \
    --cc=H.H.vanRiel@phys.uu.nl \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=linux-mm@kvack.org \
    --cc=sct@redhat.com \
    /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