| 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 linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAA6-i6rSE+PvnvmnE_6jBZvsJ+ZJmX1pSwPBE_JZw-OTotNSxQ@mail.gmail.com> Date: Tue, 10 Dec 2013 12:02:26 +0400 From: Glauber Costa <glommer@...il.com> To: Vladimir Davydov <vdavydov@...allels.com> Cc: dchinner@...hat.com, Johannes Weiner <hannes@...xchg.org>, Michal Hocko <mhocko@...e.cz>, Andrew Morton <akpm@...ux-foundation.org>, LKML <linux-kernel@...r.kernel.org>, linux-mm@...ck.org, cgroups@...r.kernel.org, devel@...nvz.org, Glauber Costa <glommer@...nvz.org> Subject: Re: [PATCH v13 00/16] kmemcg shrinkers > Please note that in contrast to previous versions this patch-set implements > slab shrinking only when we hit the user memory limit so that kmem allocations > will still fail if we are below the user memory limit, but close to the kmem > limit. This is, because the implementation of kmem-only reclaim was rather > incomplete - we had to fail GFP_NOFS allocations since everything we could > reclaim was only FS data. I will try to improve this and send in a separate > patch-set, but currently it is only worthwhile setting the kmem limit to be > greater than the user mem limit just to enable per-memcg slab accounting and > reclaim. That is unfortunate, but it makes sense as a first step. -- E Mare, Libertas -- 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