linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Rik van Riel <H.H.vanRiel@phys.uu.nl>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
	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 12:06:33 GMT	[thread overview]
Message-ID: <199811171206.MAA01194@dax.scot.redhat.com> (raw)
In-Reply-To: <Pine.LNX.3.96.981117073807.2352A-100000@mirkwood.dummy.home>

Hi,

On Tue, 17 Nov 1998 07:42:12 +0100 (CET), Rik van Riel
<H.H.vanRiel@phys.uu.nl> said:

> I meant the page aging that occurs in vmscan.c, where we
> decide on which page to unmap from a program's address
> space. 

For the last time, NO IT DOES NOT.  Read the source.  Linus removed it.
We do not use page->age AT ALL in vmscan.c in current 2.1 kernels.

> There we do aging while we don't age pages from files that are read().

For the last time, YES WE DO.  shrink_mmap() for the page cache in
mm/filemap.c still uses page aging in current 2.1 kernels.  Read() uses
the page cache.

This is a problem.

> 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 :)

This change improves low memory performance very measurably in all tests
I have tried so far.

--Stephen.
--
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-11-17 12:06 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
1998-11-17 12:06           ` Stephen C. Tweedie [this message]
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=199811171206.MAA01194@dax.scot.redhat.com \
    --to=sct@redhat.com \
    --cc=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 \
    /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