public inbox for cgroups@vger.kernel.org
 help / color / mirror / Atom feed
From: 喻望 <yuwang.yuwang-gPhfCIXyaqCqndwCJWfcng@public.gmane.org>
To: Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>,
	Michal Hocko <mhocko-AlSwsSmVLrQ@public.gmane.org>,
	Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org
Subject: memcg Can't context between v1 and v2 because css->refcnt not released
Date: Wed, 09 Aug 2017 14:44:23 +0800	[thread overview]
Message-ID: <D5B0D047.344%yuwang.yuwang@alibaba-inc.com> (raw)

Hello Johannes ,Michal,and Tejun:

  i using memcg v1,  but some reason  i want to context to  memcg v2,
but i can't, here is my step:
#cat /proc/cgroups
#subsys_name hierarchy num_cgroups enabled
 memory 5 1 1
#cd /sys/fs/cgroup/memory
#mkdir a
#echo 0 > a/cgroup.procs
#sleep 1
#echo 0 > cgroup.procs
#cat /proc/cgroups
#subsys_name hierarchy num_cgroups enabled
 memory 5 2 1  
the num_cgroups not go to "1"
so it will lead to can't context to memcg 2
#cd ..
#umount memory
umount: /sys/fs/cgroup/memory: target is busy.
        (In some cases useful info about processes that use
         the device is found by lsof(8) or fuser(1))

  and i have tracked  the root cause, i found that "b2052564e66d mm:
memcontrol: continue cache reclaim from offlined groups"from Johannes
Weiner, remove mem_cgroup_reparent_charges when mem_cgroup_css_offline, so
the css->refcount  not go to "0", so the css_release not call when rmdir
cgroup, and nr_cgroups not released.
  so i want to ask does it reasonable can't context between v1 and v2


             reply	other threads:[~2017-08-09  6:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-09  6:44 喻望 [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
     [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
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=D5B0D047.344%yuwang.yuwang@alibaba-inc.com \
    --to=yuwang.yuwang-gphfcixyaqcqndwcjwfcng@public.gmane.org \
    --cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org \
    --cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
    --cc=mhocko-AlSwsSmVLrQ@public.gmane.org \
    --cc=tj-DgEjT+Ai2ygdnm+yROfE0A@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