linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: steve@digidescorp.com
Cc: balbir@linux.vnet.ibm.com, linux-mm@kvack.org,
	dhowells@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] nommu: add anonymous page memcg accounting
Date: Wed, 20 Oct 2010 09:17:46 +0900	[thread overview]
Message-ID: <20101020091746.f0cc5dc2.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <1287512657.2500.31.camel@iscandar.digidescorp.com>

On Tue, 19 Oct 2010 13:24:17 -0500
"Steven J. Magnani" <steve@digidescorp.com> wrote:

> On Tue, 2010-10-19 at 21:18 +0530, Balbir Singh wrote:
> > * Steven J. Magnani <steve@digidescorp.com> [2010-10-19 07:34:14]:
> > 
> > > Add the necessary calls to track VM anonymous page usage (only).
> > > 
> > > V2 changes:
> > > * Added update of memory cgroup documentation
> > > * Clarify use of 'file' to distinguish anonymous mappings
> > > 
> > > Signed-off-by: Steven J. Magnani <steve@digidescorp.com>
> > > ---
> > > diff -uprN a/Documentation/cgroups/memory.txt b/Documentation/cgroups/memory.txt
> > > --- a/Documentation/cgroups/memory.txt	2010-10-05 09:14:36.000000000 -0500
> > > +++ b/Documentation/cgroups/memory.txt	2010-10-19 07:28:04.000000000 -0500
> > > @@ -34,6 +34,7 @@ Current Status: linux-2.6.34-mmotm(devel
> > > 
> > >  Features:
> > >   - accounting anonymous pages, file caches, swap caches usage and limiting them.
> > > +   NOTE: On NOMMU systems, only anonymous pages are accounted.
> > >   - private LRU and reclaim routine. (system's global LRU and private LRU
> > >     work independently from each other)
> > >   - optionally, memory+swap usage can be accounted and limited.
> > > @@ -640,7 +641,30 @@ At reading, current status of OOM is sho
> > >  	under_oom	 0 or 1 (if 1, the memory cgroup is under OOM, tasks may
> > >  				 be stopped.)
> > > 
> > > -11. TODO
> > > +11. NOMMU Support
> <snip>
> > > +
> > > +At the present time, only anonymous pages are included in NOMMU memory cgroup
> > > +accounting.
> > 
> > What is the reason for tracking just anonymous memory?
> 
> Tracking more than that is beyond my current scope, and perhaps of
> limited benefit under an assumption that NOMMU systems don't usually
> work with large files. The limitations of the implementation are
> documented, so hopefully anyone who needs more functionality will know
> that they need to implement it.
> 

What happens at reaching limit ? memory can be reclaimed ?

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>

  reply	other threads:[~2010-10-20  0:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-19 12:34 Steven J. Magnani
2010-10-19 15:48 ` Balbir Singh
2010-10-19 18:24   ` Steven J. Magnani
2010-10-20  0:17     ` KAMEZAWA Hiroyuki [this message]
2010-10-20 12:49       ` Steven J. Magnani
2010-10-21  0:08         ` KAMEZAWA Hiroyuki
2010-10-21  2:35           ` Steve Magnani
2010-10-21  2:42             ` 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=20101020091746.f0cc5dc2.kamezawa.hiroyu@jp.fujitsu.com \
    --to=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=steve@digidescorp.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