From: Balbir Singh <balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: Badari Pulavarty <pbadari-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
Paul Menage <menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Subject: Re: Unable to remove control groups on 2.6.23-rc8-mm1
Date: Wed, 26 Sep 2007 08:55:31 +0530 [thread overview]
Message-ID: <46F9D12B.7070402@linux.vnet.ibm.com> (raw)
In-Reply-To: <1190763481.13955.52.camel-Tq0y/nC7FQqofirLTBlK79w6IDGaBKkJqyM6JfAXOaQ@public.gmane.org>
Badari Pulavarty wrote:
> Hi,
>
> I am playing with control groups on 2.6.23-rc8-mm1.
>
> I am able to mount cgroup and create subgroups. I was able
> to move some tasks into them. But, after killing tasks I am
> not able to remove the subgroups. Any idea on why ?
>
> Thanks,
> Badari
>
Badari,
We account for page cache usage as well now, I suspect you
most likely have page/swap cache pages charged to the container.
You can try several options (some documented in Documentation/
controllers/memory.txt)
1. Try executing sync; echo 1 > /proc/sys/vm/drop_caches
and then remove the directory
2. Prior to assigning tasks, set memory.control_type to 1,
that tracks only RSS pages. You'll find memory.usage_in_bytes
go to zero as soon as all the tasks exit
3. Set notify_on_release and use the release_agent and releasable
to free the container once all pages charged to it are freed.
I wonder if I should provide a force_reclaim (hard to guarantee
it will work) for each container, so that the container can
be freed.
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
next prev parent reply other threads:[~2007-09-26 3:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 23:38 Unable to remove control groups on 2.6.23-rc8-mm1 Badari Pulavarty
[not found] ` <1190763481.13955.52.camel-Tq0y/nC7FQqofirLTBlK79w6IDGaBKkJqyM6JfAXOaQ@public.gmane.org>
2007-09-25 23:53 ` Paul Menage
2007-09-26 3:25 ` Balbir Singh [this message]
[not found] ` <46F9D12B.7070402-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2007-09-26 9:14 ` KAMEZAWA Hiroyuki
[not found] ` <20070926181439.93a3ef65.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2007-09-26 15:46 ` Badari Pulavarty
[not found] ` <1190821580.13955.59.camel-Tq0y/nC7FQqofirLTBlK79w6IDGaBKkJqyM6JfAXOaQ@public.gmane.org>
2007-09-26 21:37 ` KAMEZAWA Hiroyuki
2007-09-26 15:29 ` Badari Pulavarty
[not found] ` <1190820594.13955.57.camel-Tq0y/nC7FQqofirLTBlK79w6IDGaBKkJqyM6JfAXOaQ@public.gmane.org>
2007-09-26 16:39 ` Paul Menage
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=46F9D12B.7070402@linux.vnet.ibm.com \
--to=balbir-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=pbadari-r/Jw6+rmf7HQT0dZR+AlfA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.