From: Nick Piggin <nickpiggin@yahoo.com.au>
To: balbir@linux.vnet.ibm.com
Cc: Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux kernel mailing list <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Hugh Dickins <hugh@veritas.com>,
Lee Schermerhorn <Lee.Schermerhorn@hp.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Pavel Emelianov <xemul@sw.ru>,
YAMAMOTO Takashi <yamamoto@valinux.co.jp>,
Rik van Riel <riel@redhat.com>,
Christoph Lameter <clameter@sgi.com>,
"Martin J. Bligh" <mbligh@google.com>,
Andy Whitcroft <andyw@uk.ibm.com>,
Srivatsa Vaddagiri <vatsa@in.ibm.com>
Subject: Re: What can we do to get ready for memory controller merge in 2.6.25
Date: Fri, 30 Nov 2007 13:11:47 +1100 [thread overview]
Message-ID: <200711301311.48291.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <474ED005.7060300@linux.vnet.ibm.com>
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...
Thanks,
Nick
next prev parent reply other threads:[~2007-11-30 2:12 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 [this message]
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:
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=200711301311.48291.nickpiggin@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=Lee.Schermerhorn@hp.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=andyw@uk.ibm.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=clameter@sgi.com \
--cc=hugh@veritas.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@google.com \
--cc=riel@redhat.com \
--cc=vatsa@in.ibm.com \
--cc=xemul@sw.ru \
--cc=yamamoto@valinux.co.jp \
/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).