linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kamezawa.hiroyu@jp.fujitsu.com
To: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	containers@lists.osdl.org, linux-mm@kvack.org,
	balbir@linux.vnet.ibm.com, xemul@openvz.org, hugh@veritas.com
Subject: Re: Re: [RFC/PATCH] cgroup swap subsystem
Date: Thu, 6 Mar 2008 21:56:56 +0900 (JST)	[thread overview]
Message-ID: <6197904.1204808216900.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <47CFD957.3060402@mxp.nes.nec.co.jp>

>> At first look, remembering mm struct is not very good.
>> Remembering swap controller itself is better.
>
>The swap_cgroup when the page(and page_cgroup) is allocated and
>the swap_cgroup when the page is going to be swapped out may be
>different by swap_cgroup_move_task(), so I think swap_cgroup
>to be charged should be determined at the point of swapout.
>
Accounting swap against an entity which allocs anon memory is
not strange. Problem here is move_task itself.
Now, charges against anon is not moved when a task which uses it
is moved. please fix this behavior first if you think this is
problematic.

But, finally, a daemon driven by process event connector
determines the group before process starts using anon. It's
doubtful that it's worth to add complicated/costly ones.


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>

  parent reply	other threads:[~2008-03-06 12:56 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-05  5:59 Daisuke Nishimura
2008-03-05  6:36 ` Paul Menage
2008-03-06 12:20   ` Daisuke Nishimura
2008-03-05  6:53 ` KAMEZAWA Hiroyuki
2008-03-05 21:51   ` Hirokazu Takahashi
2008-03-06 11:45   ` Daisuke Nishimura
2008-03-06 12:25     ` Pavel Emelyanov
2008-03-06 12:56   ` kamezawa.hiroyu [this message]
2008-03-07  8:22     ` Daisuke Nishimura
2008-03-12 22:57     ` YAMAMOTO Takashi
2008-03-05  7:03 ` KAMEZAWA Hiroyuki
2008-03-05  7:28 ` Balbir Singh
2008-03-07  4:23   ` Daisuke Nishimura
2008-03-05  8:33 ` Pavel Emelyanov
2008-03-05  8:51   ` Daisuke Nishimura
2008-03-05 14:07   ` Hugh Dickins
2008-03-05 14:14     ` Pavel Emelyanov
2008-03-06  0:33       ` KAMEZAWA Hiroyuki
2008-03-06  0:35         ` Paul Menage
2008-03-06  8:20         ` Pavel Emelyanov
2008-03-06  8:33           ` KAMEZAWA Hiroyuki
2008-03-06  8:38             ` Pavel Emelyanov
2008-03-06  8:48               ` [Devel] " Paul Menage
2008-03-06  8:50                 ` Pavel Emelyanov
2008-03-06  8:52                   ` 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=6197904.1204808216900.kamezawa.hiroyu@jp.fujitsu.com \
    --to=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=containers@lists.osdl.org \
    --cc=hugh@veritas.com \
    --cc=linux-mm@kvack.org \
    --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