On 11/21/2013 09:22 PM, Johannes Weiner wrote: >> > It's a 8-socket/160-thread (one NUMA node per socket) system that is not >> > under memory pressure during the test. The latencies are also such that >> > vm.zone_reclaim_mode=0. > The change will definitely spread allocations out to all nodes then > and it's plausible that the remote references will hurt kernel object > allocations in a tight loop. Just to confirm, could you rerun the > test with zone_reclaim_mode enabled to make the allocator stay in the > local zones? Yeah, setting vm.zone_reclaim_mode=1 fixes it pretty instantaneously. For what it's worth, I'm pretty convinced that the numbers folks put in the SLIT tables are, at best, horribly inconsistent from system to system. At worst, they're utter fabrications not linked at all to the reality of the actual latencies. -- 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/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>