linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Zlatko Calusic <Zlatko.Calusic@CARNet.hr>
To: Rik van Riel <H.H.vanRiel@phys.uu.nl>
Cc: "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: 12 Nov 1998 23:45:42 +0100	[thread overview]
Message-ID: <87k910bkdl.fsf@atlas.CARNet.hr> (raw)
In-Reply-To: Rik van Riel's message of "Thu, 12 Nov 1998 14:39:53 +0100 (CET)"

Rik van Riel <H.H.vanRiel@phys.uu.nl> writes:

> On 12 Nov 1998, Zlatko Calusic wrote:
> > "David J. Fred" <djf@ic.net> writes:
> > 
> > > Summary: When doing large file reads from disk the system pages
> > >          unexpectedly causing moderate to severe degradation in I/O
> > >          and overall system performance even though there is plenty of
> > >          memory.
> > 
> > Page cache is definitely too aggressive on recent kernels. I
> > developed a small patch that avoids excessive swapouts. It helps
> > kswapd to have less trouble reusing pages from page cache. 
> 
> Agreed, we should do something about that.
> 
> > +			age_page(page);
> > +			age_page(page);
> >  			age_page(page);
> 
> Do I hear "priority paging"? :))
> 
> >        count_max = (limit<<2) >> (priority>>1);
> >        count_min = (limit<<2) >> (priority);
> 
> Maybe increasing these has the same effect but with
> the advantage of keeping page aging intact.
> 

Maybe, but then again maybe not.

I have a feeling that change like that could easily make kswapd a CPU
pig.

We are aging pages, so that they don't get reaped easily, and then
trying to compensate that with heavier scanning. Doesn't sound like a
good idea. Sizif's job.

But still, looks interesting, so I'm just going to compile one test
kernel with bigger count limits, for the fun's sake... :)

[Cc: Linux-MM]

Regards,
-- 
Posted by Zlatko Calusic           E-mail: <Zlatko.Calusic@CARNet.hr>
---------------------------------------------------------------------
	  A chicken is an egg's way of producing more eggs.
--
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-12 23: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 [this message]
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
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=87k910bkdl.fsf@atlas.CARNet.hr \
    --to=zlatko.calusic@carnet.hr \
    --cc=H.H.vanRiel@phys.uu.nl \
    --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