From: yamamoto@valinux.co.jp (YAMAMOTO Takashi)
To: kamezawa.hiroyu@jp.fujitsu.com
Cc: nishimura@mxp.nes.nec.co.jp, linux-mm@kvack.org,
containers@lists.osdl.org, menage@google.com,
balbir@linux.vnet.ibm.com, xemul@openvz.org
Subject: Re: [RFD][PATCH] memcg: Move Usage at Task Move
Date: Wed, 11 Jun 2008 12:44:46 +0900 (JST) [thread overview]
Message-ID: <20080611034446.4C5535A23@siro.lan> (raw)
In-Reply-To: Your message of "Wed, 11 Jun 2008 12:25:00 +0900" <20080611122500.677757c6.kamezawa.hiroyu@jp.fujitsu.com>
> I'm now considering following logic. How do you think ?
>
> Assume: move TASK from group:CURR to group:DEST.
>
> == move_task(TASK, CURR, DEST)
>
> if (DEST's limit is unlimited)
> moving TASK
> return success.
>
> usage = check_usage_of_task(TASK).
>
> /* try to reserve enough room in destionation */
> if (try_to_reserve_enough_room(DEST, usage)) {
> move TASK to DEST and move pages AMAP.
> /* usage_of_task(TASK) can be changed while we do this.
> Then, we move AMAP. */
> return success;
> }
> return failure.
> ==
AMAP means that you might leave some random charges in CURR?
i think that you can redirect new charges in TASK to DEST
so that usage_of_task(TASK) will not grow.
YAMAMOTO Takashi
--
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-11 3:44 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 [this message]
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
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=20080611034446.4C5535A23@siro.lan \
--to=yamamoto@valinux.co.jp \
--cc=balbir@linux.vnet.ibm.com \
--cc=containers@lists.osdl.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=menage@google.com \
--cc=nishimura@mxp.nes.nec.co.jp \
--cc=xemul@openvz.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