lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 21 Sep 2014 12:00:12 -0400 From: Tejun Heo <tj@...nel.org> To: Vladimir Davydov <vdavydov@...allels.com> Cc: Andrew Morton <akpm@...ux-foundation.org>, Johannes Weiner <hannes@...xchg.org>, Michal Hocko <mhocko@...e.cz>, Greg Thelen <gthelen@...gle.com>, Dave Chinner <david@...morbit.com>, Glauber Costa <glommer@...il.com>, Suleiman Souhlal <suleiman@...gle.com>, Kamezawa Hiroyuki <kamezawa.hiroyu@...fujitsu.com>, linux-kernel@...r.kernel.org, linux-mm@...ck.org, cgroups@...r.kernel.org Subject: Re: [PATCH -mm 00/14] Per memcg slab shrinkers Hello, On Sun, Sep 21, 2014 at 07:14:32PM +0400, Vladimir Davydov wrote: ... > list. This is really important, because this allows us to release > memcg_cache_id used for indexing in per-memcg arrays. If we don't do > this, the arrays will grow uncontrollably, which is really bad. Note, in > comparison to user memory reparenting, which Johannes is going to get I don't know the code well and haven't read the patches and could easilya be completely off the mark, but, if the size of slab array is the only issue, wouldn't it be easier to separate that part out? The indexing is only necessary for allocating new items, right? Can't that part be shutdown and the index freed on offline and the rest stay till release? Things like reparenting tends to add fair amount of complexity and hot path overheads which aren't necessary otherwise. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists