[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090407160014.8c545c3c.kamezawa.hiroyu@jp.fujitsu.com>
Date: Tue, 7 Apr 2009 16:00:14 +0900
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To: balbir@...ux.vnet.ibm.com
Cc: "linux-mm@...ck.org" <linux-mm@...ck.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"lizf@...fujitsu.com" <lizf@...fujitsu.com>,
Rik van Riel <riel@...riel.com>,
Bharata B Rao <bharata.rao@...ibm.com>,
Dhaval Giani <dhaval@...ux.vnet.ibm.com>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFI] Shared accounting for memory resource controller
On Tue, 7 Apr 2009 12:07:22 +0530
Balbir Singh <balbir@...ux.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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists