From: Rik van Riel <H.H.vanRiel@phys.uu.nl>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Zlatko Calusic <Zlatko.Calusic@CARNet.hr>,
"David J. Fred" <djf@ic.net>,
linux-kernel@vger.rutgers.edu, Linux-MM List <linux-mm@kvack.org>
Subject: Re: unexpected paging during large file reads in 2.1.127
Date: Tue, 17 Nov 1998 07:42:12 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.3.96.981117073807.2352A-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <199811162305.XAA07996@dax.scot.redhat.com>
On Mon, 16 Nov 1998, Stephen C. Tweedie wrote:
> On Mon, 16 Nov 1998 21:48:35 +0100 (CET), Rik van Riel
> <H.H.vanRiel@phys.uu.nl> said:
> > On Mon, 16 Nov 1998, Stephen C. Tweedie wrote:
> >> The real cure is to disable page aging in the page cache completely.
> >> Now that we have disabled it for swap, it makes absolutely no sense at
> >> all to keep it in the page cache.
>
> > This is not entirely true. There is a major difference
> > between pages in the page cache and pages that can go
> > into swap. The latter kind will always be mapped inside
> > the address space of a program (where it gets proper
> > aging and stuff)
>
> No it doesn't, that's what I'm saying. Linus removed swap page aging in
> the recent kernels. That throws the balance between swap and cache
> completely out of the window: removing the page cache aging is necessary
> to restore balance. There are many many reports of massive cache growth
> on the latest kernels as a result of this.
I meant the page aging that occurs in vmscan.c, where we
decide on which page to unmap from a program's address
space. There we do aging while we don't age pages from
files that are read().
> > Now we can get severe problems with readahead when we
> > are evicting just read-in data because it isn't mapped,
>
> No, we don't. We don't evict just-read-in data, because we mark such
> pages as PG_Referenced. It takes two complete shrink_mmap() passes
> before we can evict such pages.
OK, I can (and have for quite a while) agree with this.
Kernels with this feature and enough memory will run great,
maybe small machines (<16M) will have a bit of trouble
keeping up readahead performance (since kswapd will have
made it's round a bit fast) but those machines will have
sucky performance anyway :)
Rik -- slowly getting 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
next prev parent reply other threads:[~1998-11-17 7:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.3.96.981112143712.20473B-100000@mirkwood.dummy.home>
1998-11-12 22:45 ` Zlatko Calusic
1998-11-16 19:59 ` Stephen C. Tweedie
1998-11-16 20:48 ` Rik van Riel
1998-11-16 23:05 ` Stephen C. Tweedie
1998-11-17 1:21 ` Zlatko Calusic
1998-11-17 12:00 ` Stephen C. Tweedie
1998-11-18 22:50 ` Zlatko Calusic
1998-11-17 6:42 ` Rik van Riel [this message]
1998-11-17 12:06 ` Stephen C. Tweedie
1998-11-17 20:25 ` Rik van Riel
1998-11-16 21:56 ` Zlatko Calusic
1998-11-12 23:18 ` Zlatko Calusic
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.981117073807.2352A-100000@mirkwood.dummy.home \
--to=h.h.vanriel@phys.uu.nl \
--cc=Zlatko.Calusic@CARNet.hr \
--cc=djf@ic.net \
--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