From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kosaki.motohiro@jp.fujitsu.com, Rik van Riel <riel@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vmscan: skip freeing memory from zones with lots free
Date: Sat, 29 Nov 2008 19:55:13 +0900 (JST) [thread overview]
Message-ID: <20081129195357.813D.KOSAKI.MOTOHIRO@jp.fujitsu.com> (raw)
In-Reply-To: <20081128231933.8daef193.akpm@linux-foundation.org>
> We already tried this, or something very similar in effect, I think...
>
>
> commit 26e4931632352e3c95a61edac22d12ebb72038fe
> Author: akpm <akpm>
> Date: Sun Sep 8 19:21:55 2002 +0000
>
> [PATCH] refill the inactive list more quickly
>
> Fix a problem noticed by Ed Tomlinson: under shifting workloads the
> shrink_zone() logic will refill the inactive load too slowly.
>
> Bale out of the zone scan when we've reclaimed enough pages. Fixes a
> rarely-occurring problem wherein refill_inactive_zone() ends up
> shuffling 100,000 pages and generally goes silly.
>
> This needs to be revisited - we should go on and rebalance the lower
> zones even if we reclaimed enough pages from highmem.
>
>
>
> Then it was reverted a year or two later:
>
>
> commit 265b2b8cac1774f5f30c88e0ab8d0bcf794ef7b3
> Author: akpm <akpm>
> Date: Fri Mar 12 16:23:50 2004 +0000
>
> [PATCH] vmscan: zone balancing fix
>
> We currently have a problem with the balancing of reclaim between zones: much
> more reclaim happens against highmem than against lowmem.
>
> This patch partially fixes this by changing the direct reclaim path so it
> does not bale out of the zone walk after having reclaimed sufficient pages
> from highmem: go on to reclaim from lowmem regardless of how many pages we
> reclaimed from lowmem.
>
>
> My changelog does not adequately explain the reasons.
>
> But we don't want to rediscover these reasons in early 2010 :( Some trolling
> of the linux-mm and lkml archives around those dates might help us avoid
> a mistake here.
I hope to digg past discussion archive.
Andrew, plese wait merge this patch awhile.
--
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>
next prev parent reply other threads:[~2008-11-29 10:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-28 11:08 Rik van Riel
2008-11-28 11:30 ` Peter Zijlstra
2008-11-28 22:43 ` Johannes Weiner
2008-11-29 7:19 ` Andrew Morton
2008-11-29 10:55 ` KOSAKI Motohiro [this message]
2008-12-08 13:00 ` KOSAKI Motohiro
2008-12-08 13:03 ` KOSAKI Motohiro
2008-12-08 17:48 ` KOSAKI Motohiro
2008-12-10 5:07 ` Nick Piggin
2008-12-08 20:25 ` Rik van Riel
2008-12-10 5:09 ` Nick Piggin
2008-12-12 5:50 ` KOSAKI Motohiro
2008-11-29 16:47 ` Rik van Riel
2008-11-29 17:45 ` Andrew Morton
2008-11-29 17:58 ` Rik van Riel
2008-11-29 18:26 ` Andrew Morton
2008-11-29 18:41 ` Rik van Riel
2008-11-29 18:51 ` Andrew Morton
2008-11-29 18:59 ` Rik van Riel
2008-11-29 20:29 ` Andrew Morton
2008-11-29 21:35 ` Rik van Riel
2008-11-29 21:57 ` Andrew Morton
2008-11-29 22:07 ` 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=20081129195357.813D.KOSAKI.MOTOHIRO@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.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