From: Chris Down <chris@chrisdown.name>
To: Chunxin Zang <zangchunxin@bytedance.com>
Cc: Michal Hocko <mhocko@suse.com>,
Yafang Shao <laoar.shao@gmail.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Tejun Heo <tj@kernel.org>,
lizefan@huawei.com, Jonathan Corbet <corbet@lwn.net>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
kafai@fb.com, Song Liu <songliubraving@fb.com>,
Yonghong Song <yhs@fb.com>,
andriin@fb.com, john.fastabend@gmail.com, kpsingh@chromium.org,
Cgroups <cgroups@vger.kernel.org>,
linux-doc@vger.kernel.org, Linux MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
bpf@vger.kernel.org
Subject: Re: [External] Re: [PATCH] mm/memcontrol: Add the drop_cache interface for cgroup v2
Date: Tue, 22 Sep 2020 13:43:44 +0100 [thread overview]
Message-ID: <20200922124344.GA34296@chrisdown.name> (raw)
In-Reply-To: <CAKRVAeOjST1vJsSXMgj91=tMf1MQTeNp_dz34z=DwL7Weh0bmg@mail.gmail.com>
Chunxin Zang writes:
>Please forgive me for not being able to understand why setting
>memory.low for Type_A can solve the problem.
>In my scene, Type_A is the most important, so I will set 100G to memory.low.
>But 'memory.low' only takes effect passively when the kernel is
>reclaiming memory. It means that reclaim Type_B's memory only when
>Type_A in alloc memory slow path. This will affect Type_A's
>performance.
>We want to reclaim Type_B's memory in advance when A is expected to be busy.
That's what kswapd reclaim is for, so this distinction is meaningless without
measurements :-)
next prev parent reply other threads:[~2020-09-22 12:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 8:02 zangchunxin
2020-09-21 8:12 ` Michal Hocko
2020-09-21 10:42 ` Chris Down
2020-09-21 10:55 ` Yafang Shao
2020-09-21 11:05 ` Michal Hocko
2020-09-21 11:23 ` Yafang Shao
2020-09-21 11:36 ` Michal Hocko
2020-09-22 4:20 ` Yafang Shao
2020-09-22 7:27 ` Michal Hocko
2020-09-22 8:06 ` Yafang Shao
2020-09-22 10:01 ` Michal Hocko
2020-09-22 9:43 ` [External] " Chunxin Zang
2020-09-22 9:51 ` Chris Down
2020-09-22 10:24 ` Chunxin Zang
2020-09-22 10:42 ` Chris Down
2020-09-22 12:37 ` Chunxin Zang
2020-09-22 12:43 ` Chris Down [this message]
2020-09-23 2:35 ` Chunxin Zang
2020-09-22 19:57 ` Shakeel Butt
2020-09-23 2:40 ` Chunxin Zang
2020-09-21 15:55 ` Shakeel Butt
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=20200922124344.GA34296@chrisdown.name \
--to=chris@chrisdown.name \
--cc=akpm@linux-foundation.org \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=hannes@cmpxchg.org \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=laoar.shao@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizefan@huawei.com \
--cc=mhocko@suse.com \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=tj@kernel.org \
--cc=vdavydov.dev@gmail.com \
--cc=yhs@fb.com \
--cc=zangchunxin@bytedance.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