On Tue, Oct 14, 2014 at 12:20:36PM -0400, Johannes Weiner wrote: > On cgroup deletion, outstanding page cache charges are moved to the > parent group so that they're not lost and can be reclaimed during > pressure on/inside said parent. But this reparenting is fairly tricky > and its synchroneous nature has led to several lock-ups in the past. > > Since css iterators now also include offlined css, memcg iterators can > be changed to include offlined children during reclaim of a group, and > leftover cache can just stay put. > > There is a slight change of behavior in that charges of deleted groups > no longer show up as local charges in the parent. But they are still > included in the parent's hierarchical statistics. > > Signed-off-by: Johannes Weiner <hannes@xxxxxxxxxxx> > --- > mm/memcontrol.c | 218 +------------------------------------------------------- > 1 file changed, 1 insertion(+), 217 deletions(-) I do like the stats :-) However, as I've already mentioned, on big machines we can end up with hundred of thousands of dead css's. Iterating over all of them during reclaim may result in noticeable lags. One day we'll have to do something about that I guess. Another issue is that AFAICT currently we can't have more than 64K cgroups due to the MEM_CGROUP_ID_MAX limit. The limit exists, because we use css ids for tagging swap entries and we don't want to spend too much memory on this. May be, we should simply use the mem_cgroup pointer instead of the css id? OTOH, the reparenting code looks really ugly. And we can't easily reparent swap and kmem. So I think it's a reasonable change. Acked-by: Vladimir Davydov <vdavydov@xxxxxxxxxxxxx> -- 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>