archive mirror
 help / color / mirror / Atom feed
From: Balbir Singh <>
To: Nick Piggin <>
Cc: Linux Memory Management List <>,
	Andrew Morton <>,
	linux kernel mailing list <>,
	Peter Zijlstra <>,
	Hugh Dickins <>,
	Lee Schermerhorn <>,
	KAMEZAWA Hiroyuki <>,
	Pavel Emelianov <>,
	YAMAMOTO Takashi <>,
	Rik van Riel <>,
	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: Fri, 30 Nov 2007 08:43:35 +0530	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Nick Piggin wrote:
> On Friday 30 November 2007 01:43, Balbir Singh wrote:
>> They say better strike when the iron is hot.
>> Since we have so many people discussing the memory controller, I would
>> like to access the readiness of the memory controller for mainline
>> merge. Given that we have some time until the merge window, I'd like to
>> set aside some time (from my other work items) to work on the memory
>> controller, fix review comments and defects.
>> In the past, we've received several useful comments from Rik Van Riel,
>> Lee Schermerhorn, Peter Zijlstra, Hugh Dickins, Nick Piggin, Paul Menage
>> and code contributions and bug fixes from Hugh Dickins, Pavel Emelianov,
>> Lee Schermerhorn, YAMAMOTO-San, Andrew Morton and KAMEZAWA-San. I
>> apologize if I missed out any other names or contributions
>> At the VM-Summit we decided to try the current double LRU approach for
>> memory control. At this juncture in the space-time continuum, I seek
>> your support, feedback, comments and help to move the memory controller
> Do you have any test cases, performance numbers, etc.? And also some
> results or even anecdotes of where this is going to be used would be
> interesting...

Some test results were posted at

Some results for the RSS controller can be found in the OLS paper

and at

As far as test cases are concerned, I have a simple test case that I use
that allocates memory and touches all the allocated memory in a loop. I
can post that out if required. It uses various types of allocation

1. mmaped memory
2. anonymous memory
3. shared memory

I also run various benchmarks inside a control group, limited to 400 MB
of RAM.

One interesting that I noticed was that when I booted with mem=<some
memory> and created a container with the same <some value>. The swapout
test case ran much faster in the container (NOTE: This was prior to the
swap cache changes).

KAMEZAWA-San posted some test results on background reclaim and per zone

The simplest use cases that come to mind are

1. Memory control for containers/virtualization
2. Job Isolation

	Warm Regards,
	Balbir Singh
	Linux Technology Center

  reply	other threads:[~2007-11-30  3:14 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 [this message]
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

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