On Tuesday 11 October 2011, Andrew Morton wrote: > Russell's going to hate me, but... > > I do know that he had substantial objections to at least earlier > versions of this, and he is a guy who knows of what he speaks. > > So I would want to get a nod from rmk on this work before proceeding. > If that nod isn't available then let's please identify the issues and > see what we can do about them. I'm pretty sure that Russell's concerns were almost entirely about the ARM specific parts, which were extremely hard to figure out. The most important technical concern back in July was that the patch series at the time did not address the problem of conflicting pte flags when we remap memory as uncached on ARMv6. He had a patch to address this problem that was supposed to get merged in 3.1 and would have conflicted with the CMA patch set. Things have changed a lot since then. Russell had to revert his own patch because he found regressions using it on older machines. However, the current CMA on ARM patch AFAICT reliably fixes this problem now and does not cause the same regression on older machines. The solution used now is the one we agreed on after sitting together for a few hours with Russell, Marek, Paul McKenney and myself. If there are still concerns over the ARM specific portion of the patch series, I'm very confident that we can resolve these now (I was much less so before that meeting). What I would really want to hear from you is your opinion on the architecture independent stuff. Obviously, ARM is the most important consumer of the patch set, but I think the code has its merit on other architectures as well and most of them (maybe not parisc) should be about as simple as the x86 one that Marek posted now with v16. Arnd -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>