linux-kernel - Re: What can we do to get ready for memory controller merge in 2.6.25

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20071129104726.5698321f@cuia.boston.redhat.com>
Date:	Thu, 29 Nov 2007 10:47:26 -0500
From:	Rik van Riel <riel@...hat.com>
To:	balbir@...ux.vnet.ibm.com
Cc:	Linux Memory Management List <linux-mm@...ck.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux kernel mailing list <linux-kernel@...r.kernel.org>,
	Nick Piggin <nickpiggin@...oo.com.au>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Hugh Dickins <hugh@...itas.com>,
	Lee Schermerhorn <Lee.Schermerhorn@...com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	Pavel Emelianov <xemul@...ru>,
	YAMAMOTO Takashi <yamamoto@...inux.co.jp>,
	Christoph Lameter <clameter@....com>,
	"Martin J. Bligh" <mbligh@...gle.com>,
	Andy Whitcroft <andyw@...ibm.com>,
	Srivatsa Vaddagiri <vatsa@...ibm.com>
Subject: Re: What can we do to get ready for memory controller merge in
 2.6.25

On Thu, 29 Nov 2007 20:13:17 +0530
Balbir Singh <balbir@...ux.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.

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.

-- 
All Rights Reversed
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/