linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hillf Danton <dhillf@gmail.com>
To: Ying Han <yinghan@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Rik van Riel <riel@redhat.com>, Hugh Dickins <hughd@google.com>,
	linux-mm@kvack.org
Subject: Re: [PATCH] Revert "mm: vmscan: fix misused nr_reclaimed in shrink_mem_cgroup_zone()"
Date: Wed, 11 Apr 2012 19:55:29 +0800	[thread overview]
Message-ID: <CAJd=RBDk6-FDoaj7Ly4Cw4WoEq3tLCjmZ01vZRQgXGCyFdVDhA@mail.gmail.com> (raw)
In-Reply-To: <CALWz4iyZauXcfuepN6SE9bQpPXp5dH0XvXh6zByO_uNdWTt9ow@mail.gmail.com>

On Wed, Apr 11, 2012 at 12:44 AM, Ying Han <yinghan@google.com> wrote:
>
> There are two places where we do early break out in direct reclaim path.
>
> 1. For each priority loop after calling shrink_zones(), we check
> (sc->nr_reclaimed >= sc->nr_to_reclaim)
>
> 2. For each memcg reclaim (shrink_mem_cgroup_zone) under
> shrink_zone(), we check (nr_reclaimed >= nr_to_reclaim)
>
> The second one says "if 32 (nr_to_reclaim) pages being reclaimed from
> this memcg under high priority, break". This check is necessary here
> to prevent over pressure each memcg under shrink_zone().
>
> Regarding the reverted patch, it tries to convert the "nr_reclaimed"
> to "total_reclaimed" for outer loop (restart). First of all, it
> changes the logic by doing less work each time
> should_continue_reclaim() is true. Second, the fix is simply broken by
> decrementing nr_to_reclaim each time.
>
Got, thanks:)

-hd

--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2012-04-11 11:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-09 19:42 Ying Han
2012-04-09 19:50 ` Andrew Morton
2012-04-09 21:23   ` Ying Han
2012-04-09 22:29     ` Ying Han
2012-04-09 23:24   ` Hugh Dickins
2012-04-10  0:04     ` Andrew Morton
2012-04-10 15:00 ` Hillf Danton
2012-04-10 15:16   ` Hillf Danton
2012-04-10 16:44   ` Ying Han
2012-04-11 11:55     ` Hillf Danton [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='CAJd=RBDk6-FDoaj7Ly4Cw4WoEq3tLCjmZ01vZRQgXGCyFdVDhA@mail.gmail.com' \
    --to=dhillf@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=hughd@google.com \
    --cc=linux-mm@kvack.org \
    --cc=riel@redhat.com \
    --cc=yinghan@google.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