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: Tue, 16 Sep 2014 15:16:30 +0900 From: Tejun Heo <tj@...nel.org> To: Andrew Morton <akpm@...ux-foundation.org> Cc: Michal Hocko <mhocko@...e.cz>, Vladimir Davydov <vdavydov@...allels.com>, linux-kernel@...r.kernel.org, linux-mm@...ck.org, cgroups@...r.kernel.org, Li Zefan <lizefan@...wei.com>, "David S. Miller" <davem@...emloft.net>, Johannes Weiner <hannes@...xchg.org>, Kamezawa Hiroyuki <kamezawa.hiroyu@...fujitsu.com>, Glauber Costa <glommer@...il.com>, Pavel Emelianov <xemul@...allels.com>, Greg Thelen <gthelen@...gle.com>, Eric Dumazet <eric.dumazet@...il.com>, "Eric W. Biederman" <ebiederm@...ssion.com> Subject: Re: [PATCH RFC] memcg: revert kmem.tcp accounting Hello, Andrew. On Fri, Sep 12, 2014 at 02:43:26PM -0700, Andrew Morton wrote: > 17 files changed, 51 insertions(+), 761 deletions(-) > > Sob. > > Is there a convenient way of disabling the whole thing and adding a > please-tell-us printk? If nobody tells us for a year or two then zap. Given that we're in the process of implementing the v2 interface, I don't think it'd be wise to perturb v1 interface at this point. We're gonna have to carry around v1 code for quite some time anyway and I don't think carrying the tcp code would make whole lot of difference given that the code is likely to stay static from now on. 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