From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: [PATCH -mm] Shared Page accounting for memory cgroup (v2)
Date: Wed, 6 Jan 2010 00:22:26 +0530 [thread overview]
Message-ID: <20100105185226.GG3059@balbir.in.ibm.com> (raw)
Hi, All,
No major changes from v1, except for the use of get_mm_rss().
Kamezawa-San felt that this can be done in user space and I responded
to him with my concerns of doing it in user space. The thread
can be found at http://thread.gmane.org/gmane.linux.kernel.mm/42367.
If there are no major objections, can I ask for a merge into -mm.
Andrew, the patches are against mmotm 10 December 2009, if there
are some merge conflicts, please let me know, I can rebase after
you release the next mmotm.
Add shared accounting to memcg
From: Balbir Singh <balbir@linux.vnet.ibm.com>
Currently there is no accurate way of estimating how many pages are
shared in a memory cgroup. The accurate way of accounting shared memory
is to
1. Either follow every page rmap and track number of users
2. Iterate through the pages and use _mapcount
We take an intermediate approach (suggested by Kamezawa), we sum up
the file and anon rss of the mm's belonging to the cgroup and then
subtract the values of anon rss and file mapped. This should give
us a good estimate of the pages being shared.
The shared statistic is called memory.shared_usage_in_bytes and
does not support hierarchical information, just the information
for the current cgroup.
Signed-off-by: Balbir Singh <balbir@linux.vnet.ibm.com>
---
Documentation/cgroups/memory.txt | 6 +++++
mm/memcontrol.c | 42 ++++++++++++++++++++++++++++++++++++++
2 files changed, 48 insertions(+), 0 deletions(-)
diff --git a/Documentation/cgroups/memory.txt b/Documentation/cgroups/memory.txt
index b871f25..c2c70c9 100644
--- a/Documentation/cgroups/memory.txt
+++ b/Documentation/cgroups/memory.txt
@@ -341,6 +341,12 @@ Note:
- a cgroup which uses hierarchy and it has child cgroup.
- a cgroup which uses hierarchy and not the root of hierarchy.
+5.4 shared_usage_in_bytes
+ This data lists the number of shared bytes. The data provided
+ provides an approximation based on the anon and file rss counts
+ of all the mm's belonging to the cgroup. The sum above is subtracted
+ from the count of rss and file mapped count maintained within the
+ memory cgroup statistics (see section 5.2).
6. Hierarchy support
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index 488b644..e49b47a 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -3052,6 +3052,44 @@ static int mem_cgroup_swappiness_write(struct cgroup *cgrp, struct cftype *cft,
return 0;
}
+static u64 mem_cgroup_shared_read(struct cgroup *cgrp, struct cftype *cft)
+{
+ struct mem_cgroup *memcg = mem_cgroup_from_cont(cgrp);
+ struct cgroup_iter it;
+ struct task_struct *tsk;
+ u64 total_rss = 0, shared;
+ struct mm_struct *mm;
+ s64 val;
+
+ cgroup_iter_start(cgrp, &it);
+ val = mem_cgroup_read_stat(&memcg->stat, MEM_CGROUP_STAT_RSS);
+ val += mem_cgroup_read_stat(&memcg->stat, MEM_CGROUP_STAT_FILE_MAPPED);
+ while ((tsk = cgroup_iter_next(cgrp, &it))) {
+ if (!thread_group_leader(tsk))
+ continue;
+ mm = tsk->mm;
+ /*
+ * We can't use get_task_mm(), since mmput() its counterpart
+ * can sleep. We know that mm can't become invalid since
+ * we hold the css_set_lock (see cgroup_iter_start()).
+ */
+ if (tsk->flags & PF_KTHREAD || !mm)
+ continue;
+ total_rss += get_mm_rss(mm);
+ }
+ cgroup_iter_end(cgrp, &it);
+
+ /*
+ * We need to tolerate negative values due to the difference in
+ * time of calculating total_rss and val, but the shared value
+ * converges to the correct value quite soon depending on the changing
+ * memory usage of the workload running in the memory cgroup.
+ */
+ shared = total_rss - val;
+ shared = max_t(s64, 0, shared);
+ shared <<= PAGE_SHIFT;
+ return shared;
+}
static struct cftype mem_cgroup_files[] = {
{
@@ -3101,6 +3139,10 @@ static struct cftype mem_cgroup_files[] = {
.read_u64 = mem_cgroup_swappiness_read,
.write_u64 = mem_cgroup_swappiness_write,
},
+ {
+ .name = "shared_usage_in_bytes",
+ .read_u64 = mem_cgroup_shared_read,
+ },
};
#ifdef CONFIG_CGROUP_MEM_RES_CTLR_SWAP
--
Balbir
--
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 reply other threads:[~2010-01-05 18:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 18:52 Balbir Singh [this message]
2010-01-06 0:07 ` [PATCH -mm] Shared Page accounting for memory cgroup (v2) KAMEZAWA Hiroyuki
2010-01-06 3:07 ` Balbir Singh
2010-01-06 3:18 ` KAMEZAWA Hiroyuki
2010-01-06 3:49 ` Balbir Singh
2010-01-06 3:56 ` 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=20100105185226.GG3059@balbir.in.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).