From: Xunlei Pang <xlpang@linux.alibaba.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Roman Gushchin <guro@fb.com>,
Johannes Weiner <hannes@cmpxchg.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 1/3] mm/memcg: Fix min/low usage in propagate_protected_usage()
Date: Mon, 3 Dec 2018 22:49:18 +0800 [thread overview]
Message-ID: <1c62ec71-52de-3597-ec87-3dd8d81c4d2a@linux.alibaba.com> (raw)
In-Reply-To: <20181203115453.GO31738@dhcp22.suse.cz>
On 2018/12/3 锟斤拷锟斤拷7:54, Michal Hocko wrote:
> On Mon 03-12-18 16:01:17, Xunlei Pang wrote:
>> When usage exceeds min, min usage should be min other than 0.
>> Apply the same for low.
>
> Why? What is the actual problem.
children_min_usage tracks the total children usages under min,
it's natural that min should be added into children_min_usage
when above min, I can't image why 0 is added, is there special
history I missed?
See mem_cgroup_protected(), when usage exceeds min, emin is
calculated as "parent_emin*min/children_min_usage".
>
>> Signed-off-by: Xunlei Pang <xlpang@linux.alibaba.com>
>> ---
>> mm/page_counter.c | 12 ++----------
>> 1 file changed, 2 insertions(+), 10 deletions(-)
>>
>> diff --git a/mm/page_counter.c b/mm/page_counter.c
>> index de31470655f6..75d53f15f040 100644
>> --- a/mm/page_counter.c
>> +++ b/mm/page_counter.c
>> @@ -23,11 +23,7 @@ static void propagate_protected_usage(struct page_counter *c,
>> return;
>>
>> if (c->min || atomic_long_read(&c->min_usage)) {
>> - if (usage <= c->min)
>> - protected = usage;
>> - else
>> - protected = 0;
>> -
>> + protected = min(usage, c->min);
>> old_protected = atomic_long_xchg(&c->min_usage, protected);
>> delta = protected - old_protected;
>> if (delta)
>> @@ -35,11 +31,7 @@ static void propagate_protected_usage(struct page_counter *c,
>> }
>>
>> if (c->low || atomic_long_read(&c->low_usage)) {
>> - if (usage <= c->low)
>> - protected = usage;
>> - else
>> - protected = 0;
>> -
>> + protected = min(usage, c->low);
>> old_protected = atomic_long_xchg(&c->low_usage, protected);
>> delta = protected - old_protected;
>> if (delta)
>> --
>> 2.13.5 (Apple Git-94)
>>
>
next prev parent reply other threads:[~2018-12-03 14:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 8:01 Xunlei Pang
2018-12-03 8:01 ` [PATCH 2/3] mm/vmscan: Enable kswapd to reclaim low-protected memory Xunlei Pang
2018-12-03 11:56 ` Michal Hocko
2018-12-03 15:20 ` Xunlei Pang
2018-12-03 17:22 ` Michal Hocko
2018-12-04 2:40 ` Xunlei Pang
2018-12-04 7:25 ` Michal Hocko
2018-12-04 8:44 ` Xunlei Pang
2018-12-03 8:01 ` [PATCH 3/3] mm/memcg: Avoid reclaiming below hard protection Xunlei Pang
2018-12-03 11:57 ` Michal Hocko
2018-12-04 2:53 ` Xunlei Pang
2018-12-03 11:54 ` [PATCH 1/3] mm/memcg: Fix min/low usage in propagate_protected_usage() Michal Hocko
2018-12-03 14:49 ` Xunlei Pang [this message]
2018-12-03 18:00 ` Roman Gushchin
2018-12-05 8:58 ` Xunlei Pang
2018-12-05 23:11 ` Roman Gushchin
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=1c62ec71-52de-3597-ec87-3dd8d81c4d2a@linux.alibaba.com \
--to=xlpang@linux.alibaba.com \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
/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