From: Johannes Weiner <hannes@cmpxchg.org>
To: Yisheng Xie <xieyisheng1@huawei.com>
Cc: akpm@linux-foundation.org, mgorman@suse.de, vbabka@suse.cz,
mhocko@suse.com, riel@redhat.com, shakeelb@google.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
guohanjun@huawei.com, qiuxishi@huawei.com
Subject: Re: [PATCH v4] mm/vmscan: more restrictive condition for retry in do_try_to_free_pages
Date: Fri, 17 Mar 2017 14:39:28 -0400 [thread overview]
Message-ID: <20170317183928.GA12281@cmpxchg.org> (raw)
In-Reply-To: <1489577808-19228-1-git-send-email-xieyisheng1@huawei.com>
On Wed, Mar 15, 2017 at 07:36:48PM +0800, Yisheng Xie wrote:
> @@ -100,6 +100,9 @@ struct scan_control {
> /* Can cgroups be reclaimed below their normal consumption range? */
> unsigned int may_thrash:1;
>
> + /* Did we have any memcg protected by the low limit */
> + unsigned int memcg_low_protection:1;
These are both bad names. How about the following pair?
/*
* 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_skipped:1
unsigned int memcg_low_reclaim:1;
> @@ -2557,6 +2560,8 @@ static bool shrink_node(pg_data_t *pgdat, struct scan_control *sc)
> unsigned long scanned;
>
> if (mem_cgroup_low(root, memcg)) {
> + sc->memcg_low_protection = 1;
> +
> if (!sc->may_thrash)
> continue;
if (!sc->memcg_low_reclaim) {
sc->memcg_low_skipped = 1;
continue;
}
> mem_cgroup_events(memcg, MEMCG_LOW, 1);
> @@ -2808,7 +2813,7 @@ 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_protection && !sc->may_thrash) {
if (sc->memcg_low_skipped) {
[...]
sc->memcg_low_reclaim = 1;
goto retry;
}
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Weiner <hannes@cmpxchg.org>
To: Yisheng Xie <xieyisheng1@huawei.com>
Cc: akpm@linux-foundation.org, mgorman@suse.de, vbabka@suse.cz,
mhocko@suse.com, riel@redhat.com, shakeelb@google.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
guohanjun@huawei.com, qiuxishi@huawei.com
Subject: Re: [PATCH v4] mm/vmscan: more restrictive condition for retry in do_try_to_free_pages
Date: Fri, 17 Mar 2017 14:39:28 -0400 [thread overview]
Message-ID: <20170317183928.GA12281@cmpxchg.org> (raw)
In-Reply-To: <1489577808-19228-1-git-send-email-xieyisheng1@huawei.com>
On Wed, Mar 15, 2017 at 07:36:48PM +0800, Yisheng Xie wrote:
> @@ -100,6 +100,9 @@ struct scan_control {
> /* Can cgroups be reclaimed below their normal consumption range? */
> unsigned int may_thrash:1;
>
> + /* Did we have any memcg protected by the low limit */
> + unsigned int memcg_low_protection:1;
These are both bad names. How about the following pair?
/*
* 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_skipped:1
unsigned int memcg_low_reclaim:1;
> @@ -2557,6 +2560,8 @@ static bool shrink_node(pg_data_t *pgdat, struct scan_control *sc)
> unsigned long scanned;
>
> if (mem_cgroup_low(root, memcg)) {
> + sc->memcg_low_protection = 1;
> +
> if (!sc->may_thrash)
> continue;
if (!sc->memcg_low_reclaim) {
sc->memcg_low_skipped = 1;
continue;
}
> mem_cgroup_events(memcg, MEMCG_LOW, 1);
> @@ -2808,7 +2813,7 @@ 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_protection && !sc->may_thrash) {
if (sc->memcg_low_skipped) {
[...]
sc->memcg_low_reclaim = 1;
goto retry;
}
next prev parent reply other threads:[~2017-03-17 18:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 11:36 [PATCH v4] mm/vmscan: more restrictive condition for retry in do_try_to_free_pages Yisheng Xie
2017-03-15 11:36 ` Yisheng Xie
2017-03-15 12:41 ` Michal Hocko
2017-03-15 12:41 ` Michal Hocko
2017-03-16 9:59 ` Yisheng Xie
2017-03-16 9:59 ` Yisheng Xie
2017-03-17 14:50 ` Johannes Weiner
2017-03-17 14:50 ` Johannes Weiner
2017-03-17 18:08 ` Michal Hocko
2017-03-17 18:08 ` Michal Hocko
2017-03-17 18:39 ` Johannes Weiner [this message]
2017-03-17 18:39 ` Johannes Weiner
2017-03-17 18:45 ` Michal Hocko
2017-03-17 18:45 ` Michal Hocko
2017-03-17 20:00 ` Johannes Weiner
2017-03-17 20:00 ` Johannes Weiner
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=20170317183928.GA12281@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=akpm@linux-foundation.org \
--cc=guohanjun@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.com \
--cc=qiuxishi@huawei.com \
--cc=riel@redhat.com \
--cc=shakeelb@google.com \
--cc=vbabka@suse.cz \
--cc=xieyisheng1@huawei.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 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.