From: Daisuke Nishimura <d-nishimura@mtf.biglobe.ne.jp>
To: kamezawa.hiroyu@jp.fujitsu.com
Cc: d-nishimura@mtf.biglobe.ne.jp,
Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>,
balbir@linux.vnet.ibm.com
Subject: Re: [PATCH 3/6] memcg: charge-commit-cancel protocl
Date: Sat, 4 Oct 2008 00:25:30 +0900 [thread overview]
Message-ID: <20081004002530.776d4592.d-nishimura@mtf.biglobe.ne.jp> (raw)
In-Reply-To: <2964081.1223046917168.kamezawa.hiroyu@jp.fujitsu.com>
On Sat, 4 Oct 2008 00:15:17 +0900 (JST)
kamezawa.hiroyu@jp.fujitsu.com wrote:
> ----- Original Message -----
> >> precharge/commit/cancel can be used for other places,
> >> - shmem, (and other places need precharge.)
> >> - move_account(force_empty) etc...
> >> we'll revisit later.
> >>
> >> Changelog v5 -> v6:
> >> - added newpage_charge() and migrate_fixup().
> >> - renamed functions for swap-in from "swap" to "swapin"
> >> - add more precise description.
> >>
> >
> >I don't have any objection to this direction now, but I have one quiestion.
> >
> >Does mem_cgroup_charge_migrate_fixup need to charge a newpage,
> >while mem_cgroup_prepare_migration has charged it already?
> In migration-is-failed case, we have to charge *old page* here.
>
Ah... you are right.
Sorry for noise.
Daisuke Nishimura.
> >
> >I agree adding I/F would be good for future, but I think
> >mem_cgroup_charge_migration_fixup can be no-op function for now.
> >
> Hmm, handling failure case in explicit way may be better. Ok,
> I'll try some.
>
> Thanks,
> -Kame
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
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-10-03 15:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 7:52 [PATCH 0/6] memcg update v6 (for review and discuss) KAMEZAWA Hiroyuki
2008-10-01 7:55 ` [PATCH 1/6] atomic page_cgroup flags KAMEZAWA Hiroyuki
2008-10-06 7:42 ` Balbir Singh
2008-10-01 7:56 ` [PATCH 2/6] memcg: allocate page_cgroup at boot KAMEZAWA Hiroyuki
2008-10-02 8:49 ` [PATCH 2/6] memcg: allocate page_cgroup at boot (hunk fix) KAMEZAWA Hiroyuki
2008-10-06 16:32 ` Balbir Singh
2008-10-06 10:11 ` [PATCH 2/6] memcg: allocate page_cgroup at boot Balbir Singh
2008-10-01 7:57 ` [PATCH 3/6] memcg: charge-commit-cancel protocl KAMEZAWA Hiroyuki
2008-10-01 8:33 ` Daisuke Nishimura
2008-10-01 10:04 ` kamezawa.hiroyu
2008-10-03 10:05 ` Daisuke Nishimura
2008-10-03 15:15 ` kamezawa.hiroyu
2008-10-03 15:25 ` Daisuke Nishimura [this message]
2008-10-08 9:05 ` [RFC] memcg: handle migration by charge-commit-cancel (was " KAMEZAWA Hiroyuki
2008-10-01 7:59 ` [PATCH 4/6] memcg: new force_empty and move_account KAMEZAWA Hiroyuki
2008-10-01 16:38 ` Randy Dunlap
2008-10-02 5:13 ` KAMEZAWA Hiroyuki
2008-10-01 8:00 ` [PATCH 5/6] memcg: lazy lru freeing KAMEZAWA Hiroyuki
2008-10-09 5:39 ` Daisuke Nishimura
2008-10-09 6:26 ` KAMEZAWA Hiroyuki
2008-10-01 8:01 ` [PATCH 6/6] memcg: lazy lru addition KAMEZAWA Hiroyuki
2008-10-09 6:21 ` Daisuke Nishimura
2008-10-09 6:51 ` KAMEZAWA Hiroyuki
2008-10-02 9:02 ` [PATCH 0/6] memcg update v6 (for review and discuss) KAMEZAWA Hiroyuki
2008-10-06 17:26 ` Balbir Singh
2008-10-07 1:22 ` KAMEZAWA Hiroyuki
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=20081004002530.776d4592.d-nishimura@mtf.biglobe.ne.jp \
--to=d-nishimura@mtf.biglobe.ne.jp \
--cc=balbir@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nishimura@mxp.nes.nec.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