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

[Balbir Singh]

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

-- 
	Thanks,
	Balbir Singh
	Linux Technology Center
	IBM, ISTL
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/