From: Michal Hocko <mhocko@kernel.org>
To: Yang Shi <yang.shi@linux.alibaba.com>
Cc: hannes@cmpxchg.org, akpm@linux-foundation.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] doc: memcontrol: fix the obsolete content about force empty
Date: Thu, 3 Jan 2019 11:13:02 +0100 [thread overview]
Message-ID: <20190103101302.GI31793@dhcp22.suse.cz> (raw)
In-Reply-To: <1546459533-36247-2-git-send-email-yang.shi@linux.alibaba.com>
On Thu 03-01-19 04:05:31, Yang Shi wrote:
> We don't do page cache reparent anymore when offlining memcg, so update
> force empty related content accordingly.
>
> Cc: Michal Hocko <mhocko@suse.com>
> Cc: Johannes Weiner <hannes@cmpxchg.org>
> Signed-off-by: Yang Shi <yang.shi@linux.alibaba.com>
Thanks for the clean up.
Acked-by: Michal Hocko <mhocko@suse.com>
> ---
> Documentation/cgroup-v1/memory.txt | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/cgroup-v1/memory.txt b/Documentation/cgroup-v1/memory.txt
> index 3682e99..8e2cb1d 100644
> --- a/Documentation/cgroup-v1/memory.txt
> +++ b/Documentation/cgroup-v1/memory.txt
> @@ -70,7 +70,7 @@ Brief summary of control files.
> memory.soft_limit_in_bytes # set/show soft limit of memory usage
> memory.stat # show various statistics
> memory.use_hierarchy # set/show hierarchical account enabled
> - memory.force_empty # trigger forced move charge to parent
> + memory.force_empty # trigger forced page reclaim
> memory.pressure_level # set memory pressure notifications
> memory.swappiness # set/show swappiness parameter of vmscan
> (See sysctl's vm.swappiness)
> @@ -459,8 +459,9 @@ About use_hierarchy, see Section 6.
> the cgroup will be reclaimed and as many pages reclaimed as possible.
>
> The typical use case for this interface is before calling rmdir().
> - Because rmdir() moves all pages to parent, some out-of-use page caches can be
> - moved to the parent. If you want to avoid that, force_empty will be useful.
> + Though rmdir() offlines memcg, but the memcg may still stay there due to
> + charged file caches. Some out-of-use page caches may keep charged until
> + memory pressure happens. If you want to avoid that, force_empty will be useful.
>
> Also, note that when memory.kmem.limit_in_bytes is set the charges due to
> kernel pages will still be seen. This is not considered a failure and the
> --
> 1.8.3.1
>
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2019-01-03 10:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 20:05 [RFC PATCH 0/3] mm: memcontrol: delayed " Yang Shi
2019-01-02 20:05 ` [PATCH 1/3] doc: memcontrol: fix the obsolete content about " Yang Shi
2019-01-02 21:18 ` Shakeel Butt
2019-01-02 21:18 ` Shakeel Butt
2019-01-03 10:13 ` Michal Hocko [this message]
2019-01-02 20:05 ` [PATCH 2/3] mm: memcontrol: do not try to do swap when " Yang Shi
2019-01-02 21:45 ` Shakeel Butt
2019-01-02 21:45 ` Shakeel Butt
2019-01-03 16:56 ` Yang Shi
2019-01-03 17:03 ` Shakeel Butt
2019-01-03 17:03 ` Shakeel Butt
2019-01-03 18:19 ` Yang Shi
2019-01-02 20:05 ` [PATCH 3/3] mm: memcontrol: delay force empty to css offline Yang Shi
2019-01-03 10:12 ` [RFC PATCH 0/3] mm: memcontrol: delayed force empty Michal Hocko
2019-01-03 17:33 ` Yang Shi
2019-01-03 18:13 ` Michal Hocko
2019-01-03 18:40 ` Yang Shi
2019-01-03 18:53 ` Michal Hocko
2019-01-03 19:10 ` Yang Shi
2019-01-03 19:23 ` Michal Hocko
2019-01-03 19:49 ` Yang Shi
2019-01-03 20:01 ` Michal Hocko
2019-01-04 4:15 ` Yang Shi
2019-01-04 8:55 ` Michal Hocko
2019-01-04 16:46 ` Yang Shi
2019-01-04 20:03 ` Greg Thelen
2019-01-04 20:03 ` Greg Thelen
2019-01-04 21:41 ` Yang Shi
2019-01-04 22:57 ` Yang Shi
2019-01-04 23:04 ` Yang Shi
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=20190103101302.GI31793@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=yang.shi@linux.alibaba.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