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

[Balbir Singh <balbir@linux.vnet.ibm.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>