From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: balbir@linux.vnet.ibm.com,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Add file based RSS accounting for memory resource controller (v2)
Date: Thu, 16 Apr 2009 16:40:36 +0900 [thread overview]
Message-ID: <20090416164036.03d7347a.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20090416110246.c3fef293.kamezawa.hiroyu@jp.fujitsu.com>
On Thu, 16 Apr 2009 11:02:46 +0900
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> On Thu, 16 Apr 2009 07:29:55 +0530
> Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
>
> > Thanks, I could have almost sworn I had it.. but I clearly don't
> >
> > Here is the fixed version
> >
> > Feature: Add file RSS tracking per memory cgroup
> >
> > From: Balbir Singh <balbir@linux.vnet.ibm.com>
> >
> > Changelog v3 -> v2
> > 1. Add corresponding put_cpu() for every get_cpu()
> >
> > Changelog v2 -> v1
> >
> > 1. Rename file_rss to mapped_file
> > 2. Add hooks into mem_cgroup_move_account for updating MAPPED_FILE statistics
> > 3. Use a better name for the statistics routine.
> >
> >
> > We currently don't track file RSS, the RSS we report is actually anon RSS.
> > All the file mapped pages, come in through the page cache and get accounted
> > there. This patch adds support for accounting file RSS pages. It should
> >
> > 1. Help improve the metrics reported by the memory resource controller
> > 2. Will form the basis for a future shared memory accounting heuristic
> > that has been proposed by Kamezawa.
> >
> > Unfortunately, we cannot rename the existing "rss" keyword used in memory.stat
> > to "anon_rss". We however, add "mapped_file" data and hope to educate the end
> > user through documentation.
> >
> > Signed-off-by: Balbir Singh <balbir@linux.vnet.ibm.com>
>
> Nice feature :) Thanks.
>
> Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
>
> I'll test this today.
>
Sorry, some troubles found. Ignore above Ack. 3points now.
1. get_cpu should be after (*)
==mem_cgroup_update_mapped_file_stat()
+ int cpu = get_cpu();
+
+ if (!page_is_file_cache(page))
+ return;
+
+ if (unlikely(!mm))
+ mm = &init_mm;
+
+ mem = try_get_mem_cgroup_from_mm(mm);
+ if (!mem)
+ return;
+ ----------------------------------------(*)
+ stat = &mem->stat;
+ cpustat = &stat->cpustat[cpu];
+
+ __mem_cgroup_stat_add_safe(cpustat, MEM_CGROUP_STAT_MAPPED_FILE, val);
+ put_cpu();
+}
==
2. In above, "mem" shouldn't be got from "mm"....please get "mem" from page_cgroup.
(Because it's file cache, pc->mem_cgroup is not NULL always.)
I saw this very easily.
==
Cache: 4096
mapped_file: 20480
==
3. at force_empty().
==
+
+ cpu = get_cpu();
+ /* Update mapped_file data for mem_cgroup "from" */
+ stat = &from->stat;
+ cpustat = &stat->cpustat[cpu];
+ __mem_cgroup_stat_add_safe(cpustat, MEM_CGROUP_STAT_MAPPED_FILE, -1);
+
+ /* Update mapped_file data for mem_cgroup "to" */
+ stat = &to->stat;
+ cpustat = &stat->cpustat[cpu];
+ __mem_cgroup_stat_add_safe(cpustat, MEM_CGROUP_STAT_MAPPED_FILE, 1);
+ put_cpu();
This just breaks counter when page is not mapped. please check page_mapped().
like this:
==
if (page_is_file_cache(page) && page_mapped(page)) {
modify counter.
}
==
and call lock_page_cgroup() in mem_cgroup_update_mapped_file_stat().
This will be slow, but optimization will be very tricky and need some amount of time.
-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-16 7:41 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 12:05 Balbir Singh
2009-04-16 0:53 ` KAMEZAWA Hiroyuki
2009-04-16 1:59 ` Balbir Singh
2009-04-16 2:02 ` KAMEZAWA Hiroyuki
2009-04-16 7:40 ` KAMEZAWA Hiroyuki [this message]
2009-04-16 8:15 ` KAMEZAWA Hiroyuki
2009-04-16 12:03 ` Balbir Singh
2009-04-17 0:14 ` KAMEZAWA Hiroyuki
2009-04-17 0:17 ` KAMEZAWA Hiroyuki
2009-04-17 1:40 ` Balbir Singh
2009-04-17 2:03 ` KAMEZAWA Hiroyuki
2009-04-17 3:45 ` Balbir Singh
2009-04-17 3:49 ` KAMEZAWA Hiroyuki
2009-04-17 4:56 ` Balbir Singh
2009-04-17 5:17 ` KAMEZAWA Hiroyuki
2009-04-17 6:47 ` Balbir Singh
2009-04-17 6:56 ` KAMEZAWA Hiroyuki
2009-04-17 14:18 ` [PATCH] Add file based RSS accounting for memory resource controller (v3) Balbir Singh
2009-04-17 16:30 ` KAMEZAWA Hiroyuki
2009-04-21 3:00 ` Balbir Singh
2009-04-21 20:25 ` Andrew Morton
2009-04-22 0:02 ` KAMEZAWA Hiroyuki
2009-04-22 3:16 ` [PATCH] memcg: remove trylock_page_cgroup KAMEZAWA Hiroyuki
2009-04-22 3:41 ` Andrew Morton
2009-04-22 4:41 ` KAMEZAWA Hiroyuki
2009-04-22 6:01 ` Andrew Morton
2009-04-22 6:13 ` KAMEZAWA Hiroyuki
2009-04-22 3:19 ` [PATCH] Add file based RSS accounting for memory resource controller (v3) Balbir Singh
2009-04-16 12:14 ` [PATCH] Add file based RSS accounting for memory resource controller (v2) Balbir Singh
2009-04-16 23:57 ` KAMEZAWA Hiroyuki
2009-04-16 3:59 ` Bharata B Rao
2009-04-16 4:34 ` 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=20090416164036.03d7347a.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.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