On Tue, 12 Apr 2011, Dave Hansen wrote: > > That doesn't seem like an argument against this patch, it's an improper > > configuration unless the remote memory access has a latency of 2.1x that > > of a local access between those two nodes. If that's the case, then it's > > accurately following the ACPI spec and the VM has made its policy decision > > to enable zone_reclaim_mode as a result. > > Heh, if the kernel broke on every system that didn't follow _some_ spec, > it wouldn't boot in very many places. > > When you have a hammer, everything looks like a nail. When you're a > BIOS developer, you start thwacking at the kernel with munged ACPI > tables instead of boot options. Folks do this in the real world, and I > think if we can't put their names and addresses next to the code that > works around this, we might as well put the DMI strings of their > hardware. :) > That's why I suggested doing away with RECLAIM_DISTANCE entirely, otherwise we are relying on the SLIT always being correct when we know it's not; the policy decision in the kernel as it stands now is that we want to enable zone_reclaim_mode when remote memory access takes longer than 2x that of a local access (3x with KOSAKI-san's patch), which is something we can actually measure at boot rather than relying on the BIOS at all. Then we don't have to bother with DMI strings for specific pieces of hardware and can remove the existing ia64 and powerpc special cases. -- 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/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>