On Wed, Feb 15, 2012 at 08:28:30PM +0400, Konstantin Khlebnikov wrote: > Global memory reclaimer should't skip referencies for any pages, > even if they are shared between different cgroups. Agreed: if we reclaim from one memcg because of its limit, we want to reclaim those pages that this group is not using. If it's used by someone else, it should be evicted and refaulted by the group that needs it. If we reclaim globally, all references are "true" because we want to evict those pages that are not used by any cgroup. But if we reclaim a hierarchical subgroup, we don't want to evict pages that are shared among this hierarchy, either, even if the memcg that has the page charged to it is not using it. Bouncing the page around the hierarchy is not sensible, because it does not solve the problem of the parent hitting its limit when the sibling group will refault it in a blink of an eye. It should only be evicted if the memcg that's not using it nears its own limit, because only in that case would reclaiming the page remedy the situation. > This patch adds scan_control->current_mem_cgroup, which points to currently > shrinking sub-cgroup in hierarchy, at global reclaim it always NULL. So to be consistent, I'm wondering if we should pass sc->target_mem_cgroup - the limit-hitting hierarchy root - to page_referenced() and then have mm_match_cgroup() do a mem_cgroup_same_or_subtree() check to see if the vma is in the hierarchy rooted at sc->target_mem_cgroup. Global reclaim is handled automatically, because mm_match_cgroup() is not checked when the passed memcg is NULL, which sc->target_mem_cgroup is for global reclaim. -- 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/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>