archive mirror
 help / color / mirror / Atom feed
From: Balbir Singh <>
To: Linux Memory Management List <>
Cc: Andrew Morton <>,
	linux kernel mailing list <>,
	Nick Piggin <>,
	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: What can we do to get ready for memory controller merge in 2.6.25
Date: Thu, 29 Nov 2007 20:13:17 +0530	[thread overview]
Message-ID: <> (raw)

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

	Balbir Singh
	Linux Technology Center

             reply	other threads:[~2007-11-29 14:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-29 14:43 Balbir Singh [this message]
2007-11-29 15:47 ` What can we do to get ready for memory controller merge in 2.6.25 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

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