Hi > > -#define RECLAIM_DISTANCE 20 > > +#define RECLAIM_DISTANCE 30 > > #endif > > #ifndef PENALTY_FOR_NODE_WITH_CPUS > > #define PENALTY_FOR_NODE_WITH_CPUS (1) > > I am not sure if this makes sense, since RECLAIM_DISTANCE is supposed > to be a hardware parameter. Could you please help clarify what the > access latency of a node with RECLAIM_DISTANCE 20 to that of a node > with RECLAIM_DISTANCE 30 is? Has the hardware definition of reclaim > distance changed? Recently, Intel/AMD implemented QPI/Hypertransport on their cpus. Then, commodity server's average node distance dramatically changed and our threshold became typical case unfit. So, my intention is, commodity server continue to don't use zone_reclaim_mode. because their workload haven't been changed. 30 itself don't have strong meaning. > I suspect the side effect is the zone_reclaim_mode is not set to 1 on > bootup for the 2-4 socket machines you mention, which results in > better VM behaviour? It depend on workload. If you are using file/web/emal server (i.e. most common case), it's better. but HPC workload don't works so fine. -- 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>