On Tue 17-12-13 15:02:10, Johannes Weiner wrote: [...] > +pagecache_mempolicy_mode: > + > +This is available only on NUMA kernels. > + > +Per default, the configured memory policy is applicable to anonymous > +memory, shmem, tmpfs, etc., whereas pagecache is allocated in an > +interleaving fashion over all allowed nodes (hardbindings and > +zone_reclaim_mode excluded). > + > +The assumption is that, when it comes to pagecache, users generally > +prefer predictable replacement behavior regardless of NUMA topology > +and maximizing the cache's effectiveness in reducing IO over memory > +locality. Isn't page spreading (PF_SPREAD_PAGE) intended to do the same thing semantically? The setting is per-cpuset rather than global which makes it harder to use but essentially it tries to distribute page cache pages across all the nodes. This is really getting confusing. We have zone_reclaim_mode to keep memory local in general, pagecache_mempolicy_mode to keep page cache local and PF_SPREAD_PAGE to spread the page cache around nodes. > + > +This behavior can be changed by enabling pagecache_mempolicy_mode, in > +which case page cache allocations will be placed according to the > +configured memory policy (Documentation/vm/numa_memory_policy.txt). -- Michal Hocko SUSE Labs -- 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>