linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@conectiva.com.br>
To: Rajagopal Ananthanarayanan <ananth@sgi.com>
Cc: linux-mm@kvack.org
Subject: Re: Odd swap behavior
Date: Wed, 4 Oct 2000 18:46:25 -0300 (BRST)	[thread overview]
Message-ID: <Pine.LNX.4.21.0010041844510.1054-100000@duckman.distro.conectiva> (raw)
In-Reply-To: <39DBA38F.B2607361@sgi.com>

On Wed, 4 Oct 2000, Rajagopal Ananthanarayanan wrote:
> Rik van Riel wrote:
> > On Tue, 3 Oct 2000, Rajagopal Ananthanarayanan wrote:
> > 
> > > I'm running fairly stressful tests like dbench with lots of
> > > clients. Since the new VM changes (now in test9), I haven't
> > > noticed _any_ swap activity, in spite of the enormous memory

> > Small code changes in deactivate_page() have caused the
> > drop_behind() code to actually WORK AS ADVERTISED right
> > now, and because of that streaming IO doesn't put any
> > memory pressure on the system.
> 
> Agreed. And since the introduction of drop_behind &
> the deactivate_page() in generic_file_write, streaming I/O
> performance has become pretty good.
> 
> However, in the above I was particularly talking about
> swap behaviour on running dbench. Dbench is write intensive,
> and also has fair amount of re-writes. So, the I'm not
> sure why we still do not swap out _really_ old processes.

Please take a look at vmscan.c::refill_inactive()

Furthermore, we don't do background scanning on all
active pages, only on the unmapped ones.

This is one of the things we'll be able to fix in
2.5...

> If old pages are not swapped out, then dbench itself
> will get less than optimal amount of the page-cache during
> its run. I believe this is one of the reasons for
> dbench's poor showing with the new VM.

Agreed, but I don't see an "easy" solution for 2.4.

regards,

Rik
--
"What you're running that piece of shit Gnome?!?!"
       -- Miguel de Icaza, UKUUG 2000

http://www.conectiva.com/		http://www.surriel.com/

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

  reply	other threads:[~2000-10-04 21:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-04  0:23 Rajagopal Ananthanarayanan
2000-10-04 15:14 ` Rik van Riel
2000-10-04 21:39   ` Rajagopal Ananthanarayanan
2000-10-04 21:46     ` Rik van Riel [this message]
2000-10-04 22:05       ` Rajagopal Ananthanarayanan
2000-10-04 22:13         ` Rik van Riel
2000-10-04 23:03           ` Rajagopal Ananthanarayanan
2000-10-05  0:07             ` Rik van Riel
2000-10-05  2:31               ` Rajagopal Ananthanarayanan

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.4.21.0010041844510.1054-100000@duckman.distro.conectiva \
    --to=riel@conectiva.com.br \
    --cc=ananth@sgi.com \
    --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