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 2/3] mm/vmscan: Enable kswapd to reclaim low-protected memory
Date: Mon, 3 Dec 2018 23:20:31 +0800 [thread overview]
Message-ID: <54a3f0a6-6e7d-c620-97f2-ac567c057bc2@linux.alibaba.com> (raw)
In-Reply-To: <20181203115646.GP31738@dhcp22.suse.cz>
On 2018/12/3 锟斤拷锟斤拷7:56, Michal Hocko wrote:
> On Mon 03-12-18 16:01:18, Xunlei Pang wrote:
>> There may be cgroup memory overcommitment, it will become
>> even common in the future.
>>
>> Let's enable kswapd to reclaim low-protected memory in case
>> of memory pressure, to mitigate the global direct reclaim
>> pressures which could cause jitters to the response time of
>> lantency-sensitive groups.
>
> Please be more descriptive about the problem you are trying to handle
> here. I haven't actually read the patch but let me emphasise that the
> low limit protection is important isolation tool. And allowing kswapd to
> reclaim protected memcgs is going to break the semantic as it has been
> introduced and designed.
We have two types of memcgs: online groups(important business)
and offline groups(unimportant business). Online groups are
all configured with MAX low protection, while offline groups
are not at all protected(with default 0 low).
When offline groups are overcommitted, the global memory pressure
suffers. This will cause the memory allocations from online groups
constantly go to the slow global direct reclaim in order to reclaim
online's page caches, as kswap is not able to reclaim low-protection
memory. low is not hard limit, it's reasonable to be reclaimed by
kswapd if there's no other reclaimable memory.
>
>>
>> Signed-off-by: Xunlei Pang <xlpang@linux.alibaba.com>
>> ---
>> mm/vmscan.c | 8 ++++++++
>> 1 file changed, 8 insertions(+)
>>
>> diff --git a/mm/vmscan.c b/mm/vmscan.c
>> index 62ac0c488624..3d412eb91f73 100644
>> --- a/mm/vmscan.c
>> +++ b/mm/vmscan.c
>> @@ -3531,6 +3531,7 @@ static int balance_pgdat(pg_data_t *pgdat, int order, int classzone_idx)
>>
>> count_vm_event(PAGEOUTRUN);
>>
>> +retry:
>> do {
>> unsigned long nr_reclaimed = sc.nr_reclaimed;
>> bool raise_priority = true;
>> @@ -3622,6 +3623,13 @@ static int balance_pgdat(pg_data_t *pgdat, int order, int classzone_idx)
>> sc.priority--;
>> } while (sc.priority >= 1);
>>
>> + if (!sc.nr_reclaimed && sc.memcg_low_skipped) {
>> + sc.priority = DEF_PRIORITY;
>> + sc.memcg_low_reclaim = 1;
>> + sc.memcg_low_skipped = 0;
>> + goto retry;
>> + }
>> +
>> if (!sc.nr_reclaimed)
>> pgdat->kswapd_failures++;
>>
>> --
>> 2.13.5 (Apple Git-94)
>>
>
next prev parent reply other threads:[~2018-12-03 15:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 8:01 [PATCH 1/3] mm/memcg: Fix min/low usage in propagate_protected_usage() 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 [this message]
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
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=54a3f0a6-6e7d-c620-97f2-ac567c057bc2@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