linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.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: Wed, 8 Apr 2009 14:32:33 +0530	[thread overview]
Message-ID: <20090408090233.GH7082@balbir.in.ibm.com> (raw)
In-Reply-To: <20090408175409.eb0818db.kamezawa.hiroyu@jp.fujitsu.com>

* KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> [2009-04-08 17:54:09]:

> On Wed, 8 Apr 2009 14:19:52 +0530
> Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> 
> > * KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> [2009-04-08 17:03:41]:
> > 
> > > On Wed, 8 Apr 2009 13:18:09 +0530
> > > Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> > > 
> > > > > > 3. Using the above, we can then try to (using an algorithm you
> > > > > > proposed), try to do some work for figuring out the shared percentage.
> > > > > > 
> > > > > This is the point. At last. Why "# of shared pages" is important ?
> > > > > 
> > > > 
> > > > I posted this in my motivation yesterday. # of shared pages can help
> > > > plan the system better and the size of the cgroup. A cgroup might have
> > > > small usage_in_bytes but large number of shared pages. We need a
> > > > metric that can help figure out the fair usage of the cgroup.
> > > > 
> > > I don't fully understand but NR_FILE_MAPPED is an information in /proc/meminfo.
> > > I personally think I want to support information in /proc/meminfo per memcg.
> > > 
> > > Hmm ? then, if you add a hook, it seems
> > > == mm/rmap.c
> > >  689 void page_add_file_rmap(struct page *page)
> > >  690 {
> > >  691         if (atomic_inc_and_test(&page->_mapcount))
> > >  692                 __inc_zone_page_state(page, NR_FILE_MAPPED);
> > >  693 }
> > > ==  page_remove_rmap(struct page *page)
> > >  739                 __dec_zone_page_state(page,
> > >  740                         PageAnon(page) ? NR_ANON_PAGES : NR_FILE_MAPPED);
> > > ==
> > > 
> > > Is good place to go, maybe.
> > > 
> > > page->page_cgroup->mem_cgroup-> inc/dec counter ?
> > > 
> > > Maybe the patch itself will be simple, overhead is unknown..
> > 
> > I thought of the same thing, but then moved to the following
> > 
> > ... mem_cgroup_charge_statistics(..) {
> >  if (page_mapcount(page) == 0 && page_is_file_cache(page))
> >     __mem_cgroup_stat_add_safe(cpustat, MEM_CGROUP_STAT_FILE_RSS, val);
> > 
> > But I've not yet tested the end result
> > 
> I think 
>  - at uncharge:
>    charge_statistics is only called when FILE CACHE is removed from radix-tree.
>    mem_cgroup_uncharge() is called only when PageAnon(page).

Good point, I missed it, testing would have caught it.

>  - at charge:
>    charge_statistics is only called when FILE CACHE is added to radix-tree.
> 
> This "checking only radix-tree insert/delete" help us to remove most of overheads
> on FILE CACHE.
> 
> So, adding new hooks to page_add_file_rmap() and page_remove_rmap()
> is a way to go. (and easy to understand because we account it at the same time
> NR_FILE_MAPPED is modified.)

Agreed.

-- 
	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>

      reply	other threads:[~2009-04-08  9:03 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-07  6:37 [RFI] Shared accounting for memory resource controller Balbir Singh
2009-04-07  7:00 ` KAMEZAWA Hiroyuki
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 [this message]

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=20090408090233.GH7082@balbir.in.ibm.com \
    --to=balbir@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=bharata.rao@in.ibm.com \
    --cc=dhaval@linux.vnet.ibm.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.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;
as well as URLs for NNTP newsgroup(s).