From: Michal Hocko <mhocko-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: wang Yu <yuwang668899-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>,
Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org
Subject: Re: memcg Can't context between v1 and v2 because css->refcnt not released
Date: Thu, 10 Aug 2017 10:19:21 +0200 [thread overview]
Message-ID: <20170810081920.GG23863@dhcp22.suse.cz> (raw)
In-Reply-To: <CADK2BfwC3WDGwoDPSjX1UpwP-4fDz5fSBjdENbxn5XQL8y3K3A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[Please do not top-post]
On Thu 10-08-17 16:10:45, wang Yu wrote:
> at first ,thanks for your reply.
> but i also tested what you said, the problem is also.
> force_empty only call try_to_free_pages, not all the pages remove
> because mem_cgroup_reparent_charges moved
Right. An alternative would be dropping the page cache globaly via
/proc/sys/vm/drop_caches. Not an ideal solution but it should help.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2017-08-10 8:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 7:06 memcg Can't context between v1 and v2 because css->refcnt not released wang Yu
2017-08-10 7:10 ` Michal Hocko
[not found] ` <20170810071059.GC23863-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2017-08-10 8:10 ` wang Yu
[not found] ` <CADK2BfwC3WDGwoDPSjX1UpwP-4fDz5fSBjdENbxn5XQL8y3K3A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-08-10 8:19 ` Michal Hocko [this message]
[not found] ` <20170810081920.GG23863-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2017-08-10 8:26 ` wang Yu
2017-08-10 9:28 ` wang Yu
[not found] ` <CADK2Bfwxp3gSDrYXAxhgoYne2T=1_RyPXqQt_cGHz86dfWgsqg@mail.gmail.com>
2017-08-10 10:34 ` Michal Hocko
[not found] ` <20170810103405.GL23863-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2017-08-21 13:08 ` Johannes Weiner
-- strict thread matches above, loose matches on Subject: below --
2017-08-09 6:44 喻望
2017-08-09 3:21 喻望
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=20170810081920.GG23863@dhcp22.suse.cz \
--to=mhocko-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org \
--cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
--cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=yuwang668899-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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