From: Marcelo Tosatti <marcelo@conectiva.com.br>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: linux-mm@kvack.org
Subject: Re: [PATCH] modified memory_pressure calculation
Date: Mon, 28 May 2001 15:07:07 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.21.0105281448570.1261-100000@freak.distro.conectiva> (raw)
In-Reply-To: <3B12A515.B8B207EA@colorfullife.com>
On Mon, 28 May 2001, Manfred Spraul wrote:
> Marcelo Tosatti wrote:
> >
> > I disagree with the second hunk.
> >
> > memory_pressure is used to calculate the size of _both_ the inactive dirty
> > and clean lists.
> >
> > Since you're adding the page back to the inactive dirty list, you should
> > not increase memory_pressure.
> >
>
> Correct. And page_launder should increase memory_pressure fore each page
> it moves back into the active list.
With the current VM code we can reach a high deactivation rate under most
heavy losts. Way too high, actually.
With a lot of heavy allocator(s), the deactivation target will become high
pretty fast, and tasks will have their pages freed way too fast.
Allocators which try to free pages themselves by calling try_to_free_pages
(in __alloc_pages()) are aging the active pages, and if we have lots of
them doing that, we have a problem.
It looks correct to make page_launder() increase memory_pressure for each
page moved to the active list, but then the problem I described above will
become even worse.
--
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/
prev parent reply other threads:[~2001-05-28 18:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-27 12:30 Manfred Spraul
2001-05-27 15:58 ` Rik van Riel
2001-05-27 17:44 ` Manfred Spraul
2001-05-27 17:51 ` Rik van Riel
2001-05-27 18:24 ` Manfred Spraul
2001-05-27 18:40 ` Rik van Riel
2001-05-28 17:29 ` Marcelo Tosatti
2001-05-28 19:20 ` Manfred Spraul
2001-05-28 18:07 ` Marcelo Tosatti [this message]
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.0105281448570.1261-100000@freak.distro.conectiva \
--to=marcelo@conectiva.com.br \
--cc=linux-mm@kvack.org \
--cc=manfred@colorfullife.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