From: "Li,Rongqing" <lirongqing@baidu.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"cgroups@vger.kernel.org" <cgroups@vger.kernel.org>,
"hannes@cmpxchg.org" <hannes@cmpxchg.org>,
Andrey Ryabinin <aryabinin@virtuozzo.com>
Subject: 答复: [PATCH] mm/memcontrol.c: speed up to force empty a memory cgroup
Date: Mon, 19 Mar 2018 10:00:41 +0000 [thread overview]
Message-ID: <2AD939572F25A448A3AE3CAEA61328C23745764B@BC-MAIL-M28.internal.baidu.com> (raw)
In-Reply-To: <20180319085355.GQ23100@dhcp22.suse.cz>
> -----邮件原件-----
> 发件人: Michal Hocko [mailto:mhocko@kernel.org]
> 发送时间: 2018年3月19日 16:54
> 收件人: Li,Rongqing <lirongqing@baidu.com>
> 抄送: linux-kernel@vger.kernel.org; linux-mm@kvack.org;
> cgroups@vger.kernel.org; hannes@cmpxchg.org; Andrey Ryabinin
> <aryabinin@virtuozzo.com>
> 主题: Re: [PATCH] mm/memcontrol.c: speed up to force empty a memory
> cgroup
>
> On Mon 19-03-18 16:29:30, Li RongQing wrote:
> > mem_cgroup_force_empty() tries to free only 32 (SWAP_CLUSTER_MAX)
> > pages on each iteration, if a memory cgroup has lots of page cache, it
> > will take many iterations to empty all page cache, so increase the
> > reclaimed number per iteration to speed it up. same as in
> > mem_cgroup_resize_limit()
> >
> > a simple test show:
> >
> > $dd if=aaa of=bbb bs=1k count=3886080
> > $rm -f bbb
> > $time echo 100000000 >/cgroup/memory/test/memory.limit_in_bytes
> >
> > Before: 0m0.252s ===> after: 0m0.178s
>
> Andrey was proposing something similar [1]. My main objection was that his
> approach might lead to over-reclaim. Your approach is more conservative
> because it just increases the batch size. The size is still rather arbitrary. Same
> as SWAP_CLUSTER_MAX but that one is a commonly used unit of reclaim in
> the MM code.
>
> I would be really curious about more detailed explanation why having a
> larger batch yields to a better performance because we are doingg
> SWAP_CLUSTER_MAX batches at the lower reclaim level anyway.
>
Although SWAP_CLUSTER_MAX is used at the lower level, but the call stack of
try_to_free_mem_cgroup_pages is too long, increase the nr_to_reclaim can reduce
times of calling function[do_try_to_free_pages, shrink_zones, hrink_node ]
mem_cgroup_resize_limit
--->try_to_free_mem_cgroup_pages: .nr_to_reclaim = max(1024, SWAP_CLUSTER_MAX),
---> do_try_to_free_pages
---> shrink_zones
--->shrink_node
---> shrink_node_memcg
---> shrink_list <-------loop will happen in this place [times=1024/32]
---> shrink_page_list
> [1]
> http://lkml.kernel.org/r/20180119132544.19569-2-aryabinin@virtuozzo.co
> m
>
> >
> > Signed-off-by: Li RongQing <lirongqing@baidu.com>
> > ---
> > mm/memcontrol.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/mm/memcontrol.c b/mm/memcontrol.c index
> > 670e99b68aa6..8910d9e8e908 100644
> > --- a/mm/memcontrol.c
> > +++ b/mm/memcontrol.c
> > @@ -2480,7 +2480,7 @@ static int mem_cgroup_resize_limit(struct
> mem_cgroup *memcg,
> > if (!ret)
> > break;
> >
> > - if (!try_to_free_mem_cgroup_pages(memcg, 1,
> > + if (!try_to_free_mem_cgroup_pages(memcg, 1024,
> > GFP_KERNEL, !memsw)) {
> > ret = -EBUSY;
> > break;
> > @@ -2610,7 +2610,7 @@ static int mem_cgroup_force_empty(struct
> mem_cgroup *memcg)
> > if (signal_pending(current))
> > return -EINTR;
> >
> > - progress = try_to_free_mem_cgroup_pages(memcg, 1,
> > + progress = try_to_free_mem_cgroup_pages(memcg, 1024,
> > GFP_KERNEL, true);
> > if (!progress) {
> > nr_retries--;
> > --
> > 2.11.0
>
> --
> Michal Hocko
> SUSE Labs
next prev parent reply other threads:[~2018-03-19 10:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 8:29 Li RongQing
2018-03-19 8:53 ` Michal Hocko
2018-03-19 10:00 ` Li,Rongqing [this message]
2018-03-19 10:37 ` 答复: " Michal Hocko
2018-03-19 10:51 ` 答复: " Li,Rongqing
2018-03-19 17:51 ` David Rientjes
2018-03-20 8:39 ` Michal Hocko
2018-03-20 20:29 ` David Rientjes
2018-03-20 22:08 ` Andrey Ryabinin
2018-03-20 22:15 ` David Rientjes
2018-03-20 22:35 ` Andrey Ryabinin
2018-03-20 22:45 ` David Rientjes
2018-03-21 9:59 ` Michal Hocko
2018-03-23 2:58 ` Li,Rongqing
2018-03-23 10:08 ` Michal Hocko
2018-03-23 12:04 ` 答复: " Li,Rongqing
2018-03-23 12:29 ` Michal Hocko
2018-03-27 6:11 ` 答复: " Li,Rongqing
2018-03-23 10:34 ` Michal Hocko
2018-03-27 6:17 ` 答复: " Li,Rongqing
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=2AD939572F25A448A3AE3CAEA61328C23745764B@BC-MAIL-M28.internal.baidu.com \
--to=lirongqing@baidu.com \
--cc=aryabinin@virtuozzo.com \
--cc=cgroups@vger.kernel.org \
--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