From: Bill Huey <billh@gnuppy.monkey.org>
To: Rik van Riel <riel@conectiva.com.br>
Cc: linux-mm@kvack.org, kernelnewbies@nl.linux.org,
linux-kernel@vger.kernel.org
Subject: Re: [CFT][PATCH *] faster cache reclaim
Date: Mon, 8 Oct 2001 18:28:20 -0700 [thread overview]
Message-ID: <20011008182820.A6361@gnuppy> (raw)
In-Reply-To: <Pine.LNX.4.33L.0110082032070.26495-100000@duckman.distro.conectiva>
In-Reply-To: <Pine.LNX.4.33L.0110082032070.26495-100000@duckman.distro.conectiva>
On Mon, Oct 08, 2001 at 08:38:27PM -0300, Rik van Riel wrote:
> It also reduces the distance between inactive_shortage and
> inactive_plenty, so kswapd should spend much less time rolling
> over pages from zones we're not interested in.
>
> This patch is meant to fix the problems where heavy cache
> activity flushes out pages from the working set, while still
> allowing the cache to put some pressure on the working set.
Rik,
It work well when I pressure it under some intensive IO operations under
dpkg and made progress when previous VMs basically froze. I did have two
running programs that have large working sets which created a lot of
contention and some CPU choppiness, but possibly some per process thrash
control should allow for both to make progress. ;-)
Good work.
bill
WARNING: multiple messages have this Message-ID (diff)
From: Bill Huey <billh@gnuppy.monkey.org>
To: Rik van Riel <riel@conectiva.com.br>
Cc: linux-mm@kvack.org, kernelnewbies@nl.linux.org,
linux-kernel@vger.kernel.org
Subject: Re: [CFT][PATCH *] faster cache reclaim
Date: Mon, 8 Oct 2001 18:28:20 -0700 [thread overview]
Message-ID: <20011008182820.A6361@gnuppy> (raw)
In-Reply-To: <Pine.LNX.4.33L.0110082032070.26495-100000@duckman.distro.conectiva>
On Mon, Oct 08, 2001 at 08:38:27PM -0300, Rik van Riel wrote:
> It also reduces the distance between inactive_shortage and
> inactive_plenty, so kswapd should spend much less time rolling
> over pages from zones we're not interested in.
>
> This patch is meant to fix the problems where heavy cache
> activity flushes out pages from the working set, while still
> allowing the cache to put some pressure on the working set.
Rik,
It work well when I pressure it under some intensive IO operations under
dpkg and made progress when previous VMs basically froze. I did have two
running programs that have large working sets which created a lot of
contention and some CPU choppiness, but possibly some per process thrash
control should allow for both to make progress. ;-)
Good work.
bill
--
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-mm.org/
next prev parent reply other threads:[~2001-10-09 1:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-08 23:38 [CFT][PATCH *] faster cache reclaim Rik van Riel
2001-10-08 23:38 ` Rik van Riel
2001-10-09 1:28 ` Bill Huey [this message]
2001-10-09 1:28 ` Bill Huey
2001-10-09 23:29 ` Robert Love
2001-10-09 23:29 ` Robert Love
2001-10-10 2:04 ` Bill Huey
2001-10-10 2:04 ` Bill Huey
2001-10-09 23:49 ` Krishnakumar B
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=20011008182820.A6361@gnuppy \
--to=billh@gnuppy.monkey.org \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.