From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Rik van Riel <riel@redhat.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>,
Nick Piggin <nickpiggin@yahoo.com.au>,
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>,
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: Thu, 29 Nov 2007 21:48:47 +0530 [thread overview]
Message-ID: <474EE667.6050106@linux.vnet.ibm.com> (raw)
In-Reply-To: <20071129104726.5698321f@cuia.boston.redhat.com>
Rik van Riel wrote:
> On Thu, 29 Nov 2007 20:13:17 +0530
> Balbir Singh <balbir@linux.vnet.ibm.com> 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.
>
>> 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
>
> The memory controller code currently in -mm seems fine to me,
> especially with the changes that got committed over the last
> days making reclaim more efficient.
>
Yes, I agree. Per zone reclaim and lists have helped make the code
better. Credit goes to KAMEZAWA-San for the per zone code and to
YAMAMOTO-San for background reclaim.
> I don't think there are any bugs left that can be found by
> code inspection - only the kind of testing that the mainline
> kernel gets might shake out more bugs.
>
> I would like to see the memory controller code go into the
> mainline kernel ASAP.
>
Excellent, thanks!
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
WARNING: multiple messages have this Message-ID (diff)
From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Rik van Riel <riel@redhat.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>,
Nick Piggin <nickpiggin@yahoo.com.au>,
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>,
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: Thu, 29 Nov 2007 21:48:47 +0530 [thread overview]
Message-ID: <474EE667.6050106@linux.vnet.ibm.com> (raw)
In-Reply-To: <20071129104726.5698321f@cuia.boston.redhat.com>
Rik van Riel wrote:
> On Thu, 29 Nov 2007 20:13:17 +0530
> Balbir Singh <balbir@linux.vnet.ibm.com> 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.
>
>> 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
>
> The memory controller code currently in -mm seems fine to me,
> especially with the changes that got committed over the last
> days making reclaim more efficient.
>
Yes, I agree. Per zone reclaim and lists have helped make the code
better. Credit goes to KAMEZAWA-San for the per zone code and to
YAMAMOTO-San for background reclaim.
> I don't think there are any bugs left that can be found by
> code inspection - only the kind of testing that the mainline
> kernel gets might shake out more bugs.
>
> I would like to see the memory controller code go into the
> mainline kernel ASAP.
>
Excellent, thanks!
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
--
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>
next prev parent reply other threads:[~2007-11-29 16:19 UTC|newest]
Thread overview: 24+ 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 14:43 ` Balbir Singh
2007-11-29 15:47 ` Rik van Riel
2007-11-29 15:47 ` Rik van Riel
2007-11-29 16:18 ` Balbir Singh [this message]
2007-11-29 16:18 ` Balbir Singh
2007-11-30 2:11 ` Nick Piggin
2007-11-30 2:11 ` Nick Piggin
2007-11-30 3:13 ` Balbir Singh
2007-11-30 3:13 ` Balbir Singh
2007-11-30 10:11 ` KAMEZAWA Hiroyuki
2007-11-30 10:11 ` KAMEZAWA Hiroyuki
2007-12-05 10:50 ` KAMEZAWA Hiroyuki
2007-12-05 10:50 ` KAMEZAWA Hiroyuki
2007-12-01 7:39 ` Paul Menage
2007-12-01 7:39 ` Paul Menage
2007-12-01 9:50 ` Balbir Singh
2007-12-01 9:50 ` Balbir Singh
2007-12-01 18:36 ` Rik van Riel
2007-12-01 18:36 ` Rik van Riel
2007-12-01 19:02 ` Paul Menage
2007-12-01 19:02 ` Paul Menage
2007-12-01 19:26 ` Rik van Riel
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=474EE667.6050106@linux.vnet.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=Lee.Schermerhorn@hp.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=andyw@uk.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=nickpiggin@yahoo.com.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.