From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: balbir@linux.vnet.ibm.com
Cc: "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: Fri, 17 Apr 2009 15:56:08 +0900 [thread overview]
Message-ID: <20090417155608.eeed1f02.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20090417064726.GB3896@balbir.in.ibm.com>
On Fri, 17 Apr 2009 12:17:26 +0530
Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> > *But* we still have following code.
> > ==
> > 820 static int __mem_cgroup_try_charge(struct mm_struct *mm,
> > 821 gfp_t gfp_mask, struct mem_cgroup **memcg,
> > 822
> > 834 /*
> > 835 * We always charge the cgroup the mm_struct belongs to.
> > 836 * The mm_struct's mem_cgroup changes on task migration if the
> > 837 * thread group leader migrates. It's possible that mm is not
> > 838 * set, if so charge the init_mm (happens for pagecache usage).
> > 839 */
> > 840 mem = *memcg;
> > 841 if (likely(!mem)) {
> > 842 mem = try_get_mem_cgroup_from_mm(mm);
> > 843 *memcg = mem;
> > 844 } else {
> > 845 css_get(&mem->css);
> > 846 }
> > 847 if (unlikely(!mem))
> > 848 return 0;
> > ==
> >
> > So, for _now_, we should use this style of checking page_cgroup is used or not.
> > Until we fix/confirm try_charge() does.
> >
>
> Hmm... I think we need to fix this loop hole, if not mem, we should
> look at charging the root cgroup. I suspect !mem cases should be 0,
> I'll keep that as a TODO.
>
yes, I'd like to keep this in my mind, too.
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-17 6:56 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
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 [this message]
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=20090417155608.eeed1f02.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