linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <H.H.vanRiel@phys.uu.nl>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH] swapin readahead
Date: Tue, 1 Dec 1998 16:41:06 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.3.96.981201163806.437C-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <199812011513.PAA18172@dax.scot.redhat.com>

On Tue, 1 Dec 1998, Stephen C. Tweedie wrote:
> In article <Pine.LNX.3.96.981127001214.445A-100000@mirkwood.dummy.home>,
> Rik van Riel <H.H.vanRiel@phys.uu.nl> writes:
> 
> > here is a very first primitive version of as swapin

I am at version 3 now (4 in a few minutes?) but your
message still seems needed...

> > The checks are all needed. The first two checks are there
> > to avoid annoying messages from swap_state.c :)) 
> 
> There's a third check needed, I think, which probably accounts for the
> swap_duplicate errors people have been noting.  You need to skip pages
> which are marked as locked in the swap_lockmap, or the async page read
> may block

OK, I'll add this test and try again.

I also noted something else -- when I free a lot of memory
(80+ MB gimp picture) the system swaps itself to death.
Could that also be because of issues with locked/unlocked
swap_cache pages which in some magical way duplicate themselves
and fill up memory? I have seen 600+ MB of shared memory :(

cheers,

Rik -- now completely used to dvorak kbd layout...
+-------------------------------------------------------------------+
| Linux memory management tour guide.        H.H.vanRiel@phys.uu.nl |
| Scouting Vries cubscout leader.      http://www.phys.uu.nl/~riel/ |
+-------------------------------------------------------------------+

--
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-01 16:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-11-26 23:23 Rik van Riel
1998-12-01 15:13 ` Stephen C. Tweedie
1998-12-01 15:41   ` Rik van Riel [this message]
1998-12-01 15:51   ` Zlatko Calusic
1998-12-01 16:42     ` Rik van Riel
1998-12-01 17:20       ` Zlatko Calusic
1998-12-01 18:32         ` Rik van Riel
1998-12-02 17:35           ` Stephen C. Tweedie
1998-12-02 21:18             ` Zlatko Calusic
1998-12-03  5:25               ` Eric W. Biederman
1998-12-03  8:55                 ` Zlatko Calusic
1998-12-03 15:39                   ` Eric W. Biederman
1998-12-03 10:07                 ` Rik van Riel
1998-12-02 17:33         ` Stephen C. Tweedie
1998-12-03 14:44           ` 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=Pine.LNX.3.96.981201163806.437C-100000@mirkwood.dummy.home \
    --to=h.h.vanriel@phys.uu.nl \
    --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