linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@nl.linux.org>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linux Kernel <linux-kernel@vger.rutgers.edu>,
	Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH] 2.2.1{3,4,5} VM fix
Date: Fri, 21 Jan 2000 03:43:25 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.10.10001210337350.27593-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <Pine.LNX.4.21.0001210301470.4332-100000@alpha.random>

On Fri, 21 Jan 2000, Andrea Arcangeli wrote:

> Anyway I think to see the problem described by Rik and actually I
> think it can be fixed by killing the useless polling of 1 second
> and replacing it with an unconiditional pre-wakeup of kswapd when
> GFP touch the freepages.high watermark. This will in turn should
> also help performances and it will try to free the cache from
> inside kswapd before a process have to free it itself.

It will damage performance. We want the hysteresis provided
by freepages.{min,low,high}...

Between .low and .high the one-second poll should do
the trick, making sure that all allocations are done
without delay.

Just around .low kswapd should be unconditionally
woken up.

Between .min and .low kswapd should be woken and
__GFP_WAIT allocations should wait.

Below .min only GFP_ATOMIC and PF_MEMALLOC allocations
should be allowed.

This is how the priorities have been intended
from the start on (except that we didn't have the
waiting part in the beginning, this needed fixing
later).

regards,

Rik
--
The Internet is not a network of computers. It is a network
of people. That is its real strength.

--
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-01-21  2:43 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-19 21:15 Rik van Riel
2000-01-20 17:11 ` Andrea Arcangeli
2000-01-20 20:30   ` Rik van Riel
2000-01-21  0:42     ` Andrea Arcangeli
2000-01-21  0:56       ` Alan Cox
2000-01-21  2:08         ` Andrea Arcangeli
2000-01-21  2:43           ` Rik van Riel [this message]
2000-01-21 12:54             ` Andrea Arcangeli
2000-01-21 19:18               ` Rik van Riel
2000-01-22  2:43                 ` Andrea Arcangeli
2000-01-22  3:22                   ` Benjamin C.R. LaHaise
2000-01-22 14:02                     ` Andrea Arcangeli
2000-01-24 13:21                       ` GFP_XXX semantics (was: Re: [PATCH] 2.2.1{3,4,5} VM fix) Ingo Oeser
2000-01-24 15:08                         ` Andrea Arcangeli
2000-01-25  0:01                           ` Rik van Riel
     [not found]                       ` <Pine.LNX.4.10.10001241411310.24852-100000@nightmaster.csn. tu-chemnitz.de>
2000-01-24 13:40                         ` Andi Kleen
2000-01-21  1:12       ` [PATCH] 2.2.1{3,4,5} VM fix Rik van Riel
2000-01-21  2:01         ` Andrea Arcangeli
2000-01-21  2:36           ` Andrea Arcangeli
2000-01-21  2:37           ` Rik van Riel
2000-01-21 13:24             ` Andrea Arcangeli

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.10.10001210337350.27593-100000@mirkwood.dummy.home \
    --to=riel@nl.linux.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andrea@suse.de \
    --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