From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: balbir@linux.vnet.ibm.com
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
"lizf@cn.fujitsu.com" <lizf@cn.fujitsu.com>,
Rik van Riel <riel@surriel.com>,
Bharata B Rao <bharata.rao@in.ibm.com>,
Dhaval Giani <dhaval@linux.vnet.ibm.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFI] Shared accounting for memory resource controller
Date: Tue, 7 Apr 2009 16:00:14 +0900 [thread overview]
Message-ID: <20090407160014.8c545c3c.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20090407063722.GQ7082@balbir.in.ibm.com>
On Tue, 7 Apr 2009 12:07:22 +0530
Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> Hi, All,
>
> This is a request for input for the design of shared page accounting for
> the memory resource controller, here is what I have so far
>
In my first impression, I think simple counting is impossible.
IOW, "usage count" and "shared or not" is very different problem.
Assume a page and its page_cgroup.
Case 1)
1. a page is mapped by process-X under group-A
2. its mapped by process-Y in group-B (now, shared and charged under group-A)
3. move process-X to group-B
4. now the page is not shared.
Case 2)
swap is an object which can be shared.
Case 3)
1. a page known as "A" is mapped by process-X under group-A.
2. its mapped by process-Y under group-B(now, shared and charged under group-A)
3. Do copy-on-write by process-X.
Now, "A" is mapped only by B but accoutned under group-A.
This case is ignored intentionally, now.
Do you want to call try_charge() both against group-A and group-B
under process-X's page fault ?
There will be many many corner case.
> Motivation for shared page accounting
> -------------------------------------
> 1. Memory cgroup administrators will benefit from the knowledge of how
> much of the data is shared, it helps size the groups correctly.
> 2. We currently report only the pages brought in by the cgroup, knowledge
> of shared data will give a complete picture of the actual usage.
>
Motivation sounds good. But counting this in generic rmap will have tons of
troubles and slow-down.
I bet we should prepare a file as
/proc/<pid>/cgroup_maps
And show RSS/RSS-owned-by-us per process. Maybe this feature will be able to be
implemented in 3 days.
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:[~2009-04-07 7:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 6:37 Balbir Singh
2009-04-07 7:00 ` KAMEZAWA Hiroyuki [this message]
2009-04-07 7:18 ` Balbir Singh
2009-04-07 7:33 ` KAMEZAWA Hiroyuki
2009-04-07 8:03 ` Balbir Singh
2009-04-07 8:24 ` KAMEZAWA Hiroyuki
2009-04-07 10:10 ` Balbir Singh
2009-04-08 5:29 ` Balbir Singh
2009-04-08 6:15 ` KAMEZAWA Hiroyuki
2009-04-08 7:04 ` Balbir Singh
2009-04-08 7:07 ` KAMEZAWA Hiroyuki
2009-04-08 7:11 ` Balbir Singh
2009-04-08 7:18 ` KAMEZAWA Hiroyuki
2009-04-08 7:31 ` Bharata B Rao
2009-04-08 7:34 ` KAMEZAWA Hiroyuki
2009-04-08 7:45 ` Bharata B Rao
2009-04-08 7:52 ` Dhaval Giani
2009-04-08 7:39 ` KAMEZAWA Hiroyuki
2009-04-08 7:48 ` Balbir Singh
2009-04-08 8:03 ` KAMEZAWA Hiroyuki
2009-04-08 8:49 ` Balbir Singh
2009-04-08 8:54 ` KAMEZAWA Hiroyuki
2009-04-08 9:02 ` 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=20090407160014.8c545c3c.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=bharata.rao@in.ibm.com \
--cc=dhaval@linux.vnet.ibm.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=riel@surriel.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