All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Rik van Riel <riel@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	safari-kernel@safari.iki.fi
Subject: Re: [PATCH] prevent kswapd from freeing excessive amounts of lowmem
Date: Thu, 6 Sep 2007 15:34:26 -0700	[thread overview]
Message-ID: <20070906153426.a173f8e2.akpm@linux-foundation.org> (raw)
In-Reply-To: <46E02CF5.3020301@redhat.com>

> On Thu, 06 Sep 2007 12:38:13 -0400 Rik van Riel <riel@redhat.com> wrote:
> Andrew Morton wrote:
> 

(What happened to the other stuff I said?)

> > I guess for a very small upper zone and a very large lower zone this could
> > still put the scan balancing out of whack, fixable by a smarter version of
> > "8*zone->pages_high" but it doesn't seem very likely that this will affect
> > things much.
> > 
> > Why doesn't direct reclaim need similar treatment?
> 
> Because we only go into the direct reclaim path once
> every zone is at or below zone->pages_low, and the
> direct reclaim path will exit once we have freed more
> than swap_cluster_max pages.
> 

hm.  Now I need to remember why direct-reclaim does that :(

WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Rik van Riel <riel@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	safari-kernel@safari.iki.fi
Subject: Re: [PATCH] prevent kswapd from freeing excessive amounts of lowmem
Date: Thu, 6 Sep 2007 15:34:26 -0700	[thread overview]
Message-ID: <20070906153426.a173f8e2.akpm@linux-foundation.org> (raw)
In-Reply-To: <46E02CF5.3020301@redhat.com>

> On Thu, 06 Sep 2007 12:38:13 -0400 Rik van Riel <riel@redhat.com> wrote:
> Andrew Morton wrote:
> 

(What happened to the other stuff I said?)

> > I guess for a very small upper zone and a very large lower zone this could
> > still put the scan balancing out of whack, fixable by a smarter version of
> > "8*zone->pages_high" but it doesn't seem very likely that this will affect
> > things much.
> > 
> > Why doesn't direct reclaim need similar treatment?
> 
> Because we only go into the direct reclaim path once
> every zone is at or below zone->pages_low, and the
> direct reclaim path will exit once we have freed more
> than swap_cluster_max pages.
> 

hm.  Now I need to remember why direct-reclaim does that :(

--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2007-09-06 22:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-05 23:01 [PATCH] prevent kswapd from freeing excessive amounts of lowmem Rik van Riel
2007-09-06  1:23 ` Andrew Morton
2007-09-06  1:23   ` Andrew Morton
2007-09-06 16:38   ` Rik van Riel
2007-09-06 16:38     ` Rik van Riel
2007-09-06 22:34     ` Andrew Morton [this message]
2007-09-06 22:34       ` Andrew Morton
2007-09-06 22:47       ` Rik van Riel
2007-09-06 22:47         ` Rik van Riel
2007-09-07 12:24 ` Pavel Machek
2007-09-07 12:24   ` Pavel Machek
2007-09-08 20:20   ` Rik van Riel
2007-09-08 20:20     ` Rik van Riel

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=20070906153426.a173f8e2.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=riel@redhat.com \
    --cc=safari-kernel@safari.iki.fi \
    /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.