From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: Paul Menage <menage@google.com>,
yamamoto@valinux.co.jp, nishimura@mxp.nes.nec.co.jp,
linux-mm@kvack.org, containers@lists.osdl.org,
balbir@linux.vnet.ibm.com, xemul@openvz.org
Subject: Re: [RFD][PATCH] memcg: Move Usage at Task Move
Date: Fri, 13 Jun 2008 09:34:36 +0900 [thread overview]
Message-ID: <20080613093436.ca1a6ded.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20080612210812.GA22948@us.ibm.com>
On Thu, 12 Jun 2008 16:08:12 -0500
"Serge E. Hallyn" <serue@us.ibm.com> wrote:
> > Assume a thread group contains threadA, threadB, threadC.
> >
> > I wanted to ask "Can threadA, and threadB, and threadC
> > be in different cgroups ? And if so, how ns cgroup handles it ?"
> >
> > Maybe I don't understand ns cgroup.
>
> In part yes, but nonetheless a very interesting question when it comes
> to composition of cgroups!
>
> Yes, you can have threads in different cgroups. The ns cgroup just
> tracks nsproxy unshares. So if you run the attached program and look
> around, you'll see the first thread is in /cg/taskpid while the second
> one is in /cg/taskpid/secondthreadpid.
>
> Clearly, composing this with a cgroup which needs to keep threads in the
> same cgroup becomes problematic!
>
> Interesting :)
>
Thank you for kindly explanation. I'll take this into account. I confirmed
memory resouce controller should not get tasks's cgroup directly from "task"
and should get it from "mm->owner".
Thank you.
Regards,
-Kame
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-06-13 0:34 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 1:52 KAMEZAWA Hiroyuki
2008-06-10 5:50 ` YAMAMOTO Takashi
2008-06-10 8:13 ` KAMEZAWA Hiroyuki
2008-06-10 12:57 ` YAMAMOTO Takashi
2008-06-11 2:02 ` KAMEZAWA Hiroyuki
2008-06-11 3:45 ` YAMAMOTO Takashi
2008-06-11 4:08 ` KAMEZAWA Hiroyuki
2008-06-10 7:35 ` Daisuke Nishimura
2008-06-10 8:26 ` KAMEZAWA Hiroyuki
2008-06-11 3:03 ` Daisuke Nishimura
2008-06-11 3:25 ` KAMEZAWA Hiroyuki
2008-06-11 3:44 ` YAMAMOTO Takashi
2008-06-11 4:14 ` KAMEZAWA Hiroyuki
2008-06-11 4:29 ` Daisuke Nishimura
2008-06-11 4:40 ` KAMEZAWA Hiroyuki
2008-06-12 5:20 ` YAMAMOTO Takashi
2008-06-12 6:51 ` KAMEZAWA Hiroyuki
2008-06-11 7:17 ` Paul Menage
2008-06-11 7:45 ` KAMEZAWA Hiroyuki
2008-06-11 8:04 ` Paul Menage
2008-06-11 8:27 ` KAMEZAWA Hiroyuki
2008-06-11 8:48 ` Paul Menage
2008-06-12 5:08 ` KAMEZAWA Hiroyuki
2008-06-12 13:17 ` Serge E. Hallyn
2008-06-12 13:34 ` kamezawa.hiroyu
2008-06-12 21:08 ` Serge E. Hallyn
2008-06-13 0:34 ` KAMEZAWA Hiroyuki [this message]
2008-06-13 0:41 ` KAMEZAWA Hiroyuki
2008-06-11 8:27 ` Balbir Singh
2008-06-11 12:21 ` Daisuke Nishimura
2008-06-11 12:51 ` kamezawa.hiroyu
2008-06-11 13:13 ` Balbir Singh
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=20080613093436.ca1a6ded.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=containers@lists.osdl.org \
--cc=linux-mm@kvack.org \
--cc=menage@google.com \
--cc=nishimura@mxp.nes.nec.co.jp \
--cc=serue@us.ibm.com \
--cc=xemul@openvz.org \
--cc=yamamoto@valinux.co.jp \
/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