From: Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Ying Han <yinghan@google.com>
Cc: Michal Hocko <mhocko@suse.cz>,
Johannes Weiner <hannes@cmpxchg.org>,
Rik van Riel <riel@redhat.com>, Hillf Danton <dhillf@gmail.com>,
Hugh Dickins <hughd@google.com>, Greg Thelen <gthelen@google.com>,
Dan Magenheimer <dan.magenheimer@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org
Subject: Re: [PATCH 3/5] mm: memcg detect no memcgs above softlimit under zone reclaim.
Date: Mon, 18 Jun 2012 11:54:15 +0900 [thread overview]
Message-ID: <4FDE9857.7000801@jp.fujitsu.com> (raw)
In-Reply-To: <1339007031-10527-1-git-send-email-yinghan@google.com>
(2012/06/07 3:23), Ying Han wrote:
> In memcg kernel, cgroup under its softlimit is not targeted under global
> reclaim. It could be possible that all memcgs are under their softlimit for
> a particular zone. If that is the case, the current implementation will
> burn extra cpu cycles without making forward progress.
>
> The idea is from LSF discussion where we detect it after the first round of
> scanning and restart the reclaim by not looking at softlimit at all. This
> allows us to make forward progress on shrink_zone().
>
> Signed-off-by: Ying Han<yinghan@google.com>
Hm, how about adding sc->ignore_softlimit and preserve the result among priority loops ?
Is it better to check 'ignore_softlimit' at every priority updates ?
Thanks,
-Kame
> ---
> mm/vmscan.c | 18 ++++++++++++++++--
> 1 files changed, 16 insertions(+), 2 deletions(-)
>
> diff --git a/mm/vmscan.c b/mm/vmscan.c
> index 0560783..5d036f5 100644
> --- a/mm/vmscan.c
> +++ b/mm/vmscan.c
> @@ -2142,6 +2142,10 @@ static void shrink_zone(int priority, struct zone *zone,
> .priority = priority,
> };
> struct mem_cgroup *memcg;
> + bool over_softlimit, ignore_softlimit = false;
> +
> +restart:
> + over_softlimit = false;
>
> memcg = mem_cgroup_iter(root, NULL,&reclaim);
> do {
> @@ -2163,9 +2167,14 @@ static void shrink_zone(int priority, struct zone *zone,
> * we have to reclaim under softlimit instead of burning more
> * cpu cycles.
> */
> - if (!global_reclaim(sc) || priority< DEF_PRIORITY - 2 ||
> - should_reclaim_mem_cgroup(memcg))
> + if (ignore_softlimit || !global_reclaim(sc) ||
> + priority< DEF_PRIORITY - 2 ||
> + should_reclaim_mem_cgroup(memcg)) {
> shrink_mem_cgroup_zone(priority,&mz, sc);
> +
> + over_softlimit = true;
> + }
> +
> /*
> * Limit reclaim has historically picked one memcg and
> * scanned it with decreasing priority levels until
> @@ -2182,6 +2191,11 @@ static void shrink_zone(int priority, struct zone *zone,
> }
> memcg = mem_cgroup_iter(root, memcg,&reclaim);
> } while (memcg);
> +
> + if (!over_softlimit) {
> + ignore_softlimit = true;
> + goto restart;
> + }
> }
>
> /* Returns true if compaction should go ahead for a high-order request */
--
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:[~2012-06-18 2:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 18:23 Ying Han
2012-06-18 2:54 ` Kamezawa Hiroyuki [this message]
2012-06-18 16:30 ` Ying Han
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=4FDE9857.7000801@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=dan.magenheimer@oracle.com \
--cc=dhillf@gmail.com \
--cc=gthelen@google.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--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