archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <>
To: "Paul Menage" <>
	"Nick Piggin" <>,
	"Linux Memory Management List" <>,
	"Andrew Morton" <>,
	"linux kernel mailing list" <>,
	"Peter Zijlstra" <>,
	"Hugh Dickins" <>,
	"Lee Schermerhorn" <>,
	"KAMEZAWA Hiroyuki" <>,
	"Pavel Emelianov" <>,
	"YAMAMOTO Takashi" <>,
	"Christoph Lameter" <>,
	"Martin J. Bligh" <>,
	"Andy Whitcroft" <>,
	"Srivatsa Vaddagiri" <>
Subject: Re: What can we do to get ready for memory controller merge in 2.6.25
Date: Sat, 1 Dec 2007 14:26:50 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Sat, 1 Dec 2007 11:02:32 -0800
"Paul Menage" <> wrote:

> On Dec 1, 2007 10:36 AM, Rik van Riel <> wrote:
> >
> > With the /proc/refaults info, we can measure how much extra
> > memory each process group needs, if any.
> What's the status of that? It looks as though it would be better than
> the "accessed in the last N seconds" metric that we've been playing
> with, although it's possibly more intrusive?
> Would it be practical to keep a non-resident set for each cgroup?

I have an implementation with a global array, but will have to
change it over to a per-radix tree implementation (not that
hard, with the slab reclaiming code) and per-cgroup reclaiming

That way we can figure out per mapping, per cgroup or system
wide reclaim info (though not all at the same time).

> > As for how much memory a process group needs, at pageout time
> > we can check the fraction of pages that are accessed.  If 60%
> > of the pages were recently accessed at pageout time and this
> > process group is spending little or no time waiting for refaults,
> > 40% of the pages are *not* recently accessed and we can probably
> > reduce the amount of memory assigned to this group.
> It would probably be better to reduce its background-reclaim high
> watermark than to reduce its limit. If you do the latter, you risk
> triggering an OOM in the cgroup if it turns out that it did need all
> that memory after all.

I did mean the RSS limit, not a virtual memory limit.

What exactly are all the terminologies you use that
I need to be aware of? :)

"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan

      reply	other threads:[~2007-12-01 19:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-29 14:43 What can we do to get ready for memory controller merge in 2.6.25 Balbir Singh
2007-11-29 15:47 ` Rik van Riel
2007-11-29 16:18   ` Balbir Singh
2007-11-30  2:11 ` Nick Piggin
2007-11-30  3:13   ` Balbir Singh
2007-11-30 10:11     ` KAMEZAWA Hiroyuki
2007-12-05 10:50       ` KAMEZAWA Hiroyuki
2007-12-01  7:39   ` Paul Menage
2007-12-01  9:50     ` Balbir Singh
2007-12-01 18:36       ` Rik van Riel
2007-12-01 19:02         ` Paul Menage
2007-12-01 19:26           ` Rik van Riel [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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).