From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: balbir@linux.vnet.ibm.com
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"menage@google.com" <menage@google.com>,
"containers@lists.osdl.org" <containers@lists.osdl.org>
Subject: Re: Question : memrlimit cgroup's task_move (2.6.26-rc5-mm3)
Date: Thu, 19 Jun 2008 12:24:29 +0900 [thread overview]
Message-ID: <20080619122429.138a1d32.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <4859CEE7.9030505@linux.vnet.ibm.com>
On Thu, 19 Jun 2008 08:43:43 +0530
Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
>
> > I think the charge of the new group goes to minus. right ?
> > (and old group's charge never goes down.)
> > I don't think this is "no problem".
> >
> > What kind of patch is necessary to fix this ?
> > task_attach() should be able to fail in future ?
> >
> > I'm sorry if I misunderstand something or this is already in TODO list.
> >
>
> It's already on the TODO list. Thanks for keeping me reminded about it.
>
Okay, I'm looking foward to see how can_attach and roll-back(if necessary)
is implemnted.
As you know, I'm interested in how to handle failure of task move.
Thanks,
-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-19 3:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 3:14 KAMEZAWA Hiroyuki
2008-06-19 3:13 ` Balbir Singh
2008-06-19 3:24 ` KAMEZAWA Hiroyuki [this message]
2008-06-19 10:22 ` KAMEZAWA Hiroyuki
2008-06-19 12:30 ` Balbir Singh
2008-06-19 13:38 ` kamezawa.hiroyu
2008-06-19 16:41 ` Balbir Singh
2008-06-19 18:25 ` Balbir Singh
2008-06-20 0:13 ` KAMEZAWA Hiroyuki
2008-06-20 13:33 ` 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=20080619122429.138a1d32.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 \
/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