From: Michal Hocko <mhocko@kernel.org>
To: Yisheng Xie <ysxie@foxmail.com>
Cc: akpm@linux-foundation.org, hannes@cmpxchg.org, mgorman@suse.de,
vbabka@suse.cz, riel@redhat.com, shakeelb@google.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
xieyisheng1@huawei.com, guohanjun@huawei.com,
qiuxishi@huawei.com
Subject: Re: [PATCH v5] mm/vmscan: more restrictive condition for retry in do_try_to_free_pages
Date: Wed, 22 Mar 2017 10:54:15 -0400 [thread overview]
Message-ID: <20170322145413.GA10290@dhcp22.suse.cz> (raw)
In-Reply-To: <1490191893-5923-1-git-send-email-ysxie@foxmail.com>
On Wed 22-03-17 22:11:33, Yisheng Xie wrote:
> From: Yisheng Xie <xieyisheng1@huawei.com>
>
> By reviewing code, I find that when enter do_try_to_free_pages, the
> may_thrash is always clear, and it will retry shrink zones to tap
> cgroup's reserves memory by setting may_thrash when the former
> shrink_zones reclaim nothing.
>
> However, when memcg is disabled or on legacy hierarchy, or there do not
> have any memcg protected by low limit, it should not do this useless
> retry at all, for we do not have any cgroup's reserves memory to tap,
> and we have already done hard work but made no progress, which as Michal
> pointed out in former version, we are trying hard to control the retry
> logical of page alloctor, and the current additional round of reclaim is
> just lame.
>
> Therefore, to avoid this unneeded retrying and make code more readable,
> we remove the may_thrash field in scan_control, instead, introduce
> memcg_low_reclaim and memcg_low_skipped, and only retry when
> memcg_low_skipped, by setting memcg_low_reclaim.
>
> Signed-off-by: Yisheng Xie <xieyisheng1@huawei.com>
> Acked-by: Michal Hocko <mhocko@suse.com>
> Suggested-by: Johannes Weiner <hannes@cmpxchg.org>
> Suggested-by: Michal Hocko <mhocko@kernel.org>
> Suggested-by: Shakeel Butt <shakeelb@google.com>
> Reviewed-by: Shakeel Butt <shakeelb@google.com>
Yes, the naming is much better now. Btw. Acked-by tags should be usually
dropped after the patch is reworked. But I am OK with keeping it in this
particular case.
Thanks!
> ---
> v5:
> - remove may_thrash field in scan_control, and introduce mem_cgroup_reclaim
> and memcg_low_skipped to make code more readable. - Johannes
>
> v4:
> - add a new field in scan_control named memcg_low_protection to check whether
> there have any memcg protected by low limit. - Michal
>
> v3:
> - rename function may_thrash() to mem_cgroup_thrashed() to avoid confusing.
>
> v2:
> - more restrictive condition for retry of shrink_zones (restricting
> cgroup_disabled=memory boot option and cgroup legacy hierarchy) - Shakeel
>
> - add a stub function may_thrash() to avoid compile error or warning.
>
> - rename subject from "donot retry shrink zones when memcg is disable"
> to "more restrictive condition for retry in do_try_to_free_pages"
>
> Any comment is more than welcome!
>
> Hi, Andrew,
> Could you please help to drop the v4, thank you so much.
>
> Thanks
> Yisheng Xie
>
> mm/vmscan.c | 18 +++++++++++++-----
> 1 file changed, 13 insertions(+), 5 deletions(-)
>
> diff --git a/mm/vmscan.c b/mm/vmscan.c
> index bc8031e..d214212 100644
> --- a/mm/vmscan.c
> +++ b/mm/vmscan.c
> @@ -97,8 +97,13 @@ struct scan_control {
> /* Can pages be swapped as part of reclaim? */
> unsigned int may_swap:1;
>
> - /* Can cgroups be reclaimed below their normal consumption range? */
> - unsigned int may_thrash:1;
> + /*
> + * Cgroups are not reclaimed below their configured memory.low,
> + * unless we threaten to OOM. If any cgroups are skipped due to
> + * memory.low and nothing was reclaimed, go back for memory.low.
> + */
> + unsigned int memcg_low_reclaim:1;
> + unsigned int memcg_low_skipped:1;
>
> unsigned int hibernation_mode:1;
>
> @@ -2557,8 +2562,10 @@ static bool shrink_node(pg_data_t *pgdat, struct scan_control *sc)
> unsigned long scanned;
>
> if (mem_cgroup_low(root, memcg)) {
> - if (!sc->may_thrash)
> + if (!sc->memcg_low_reclaim) {
> + sc->memcg_low_skipped = 1;
> continue;
> + }
> mem_cgroup_events(memcg, MEMCG_LOW, 1);
> }
>
> @@ -2808,9 +2815,10 @@ static unsigned long do_try_to_free_pages(struct zonelist *zonelist,
> return 1;
>
> /* Untapped cgroup reserves? Don't OOM, retry. */
> - if (!sc->may_thrash) {
> + if (sc->memcg_low_skipped) {
> sc->priority = initial_priority;
> - sc->may_thrash = 1;
> + sc->memcg_low_reclaim = 1;
> + sc->memcg_low_skipped = 0;
> goto retry;
> }
>
> --
> 1.9.1
>
> --
> 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>
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2017-03-22 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 14:11 [PATCH v5] mm/vmscan: more restrictive condition for retry in do_try_to_free_pages Yisheng Xie
2017-03-22 14:43 ` Johannes Weiner
2017-03-22 14:54 ` Michal Hocko [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=20170322145413.GA10290@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=guohanjun@huawei.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=qiuxishi@huawei.com \
--cc=riel@redhat.com \
--cc=shakeelb@google.com \
--cc=vbabka@suse.cz \
--cc=xieyisheng1@huawei.com \
--cc=ysxie@foxmail.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;
as well as URLs for NNTP newsgroup(s).