On Sat, Apr 10, 2010 at 10:00:37PM +0200, Andrea Arcangeli wrote: > and we need it to use non temporal stores, but even that will be To clarify, I mean using temporal stores only on the CPUs with <8M L2 caches, with some of the Xeon preloading the cache may provide an even further boost to the child with hugepages in addition to the further longstanding benefits of hugetlb for long lived allocations. Furthermore there is also an option (only available when DEBUG_VM is on, called transparent_hugepage/debug_cow) to COW with 4k copies (exactly like we have to do if cow fails to allocate an hugepage, it's the cow fallback) that already eliminates any chance for slowdown in practice, but I don't recommend it at all, because it may provide a minor speedup immediately after the cow with l2 cache <4M, but then it slowdown the child forever and eliminates the more important longstanding benefits. And this in general is very nitpick at this point, but I just wanted to cover all the details I'm aware about of the subtopic you mentioned for completeness. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>