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
| ||
|
Date: Fri, 29 May 2015 09:10:55 -0400 From: Tejun Heo <tj@...nel.org> To: Michal Hocko <mhocko@...e.cz> Cc: Johannes Weiner <hannes@...xchg.org>, linux-mm@...ck.org, Oleg Nesterov <oleg@...hat.com>, Vladimir Davydov <vdavydov@...allels.com>, KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>, KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>, Andrew Morton <akpm@...ux-foundation.org>, LKML <linux-kernel@...r.kernel.org> Subject: Re: [RFC 3/3] memcg: get rid of mm_struct::owner On Fri, May 29, 2015 at 02:08:38PM +0200, Michal Hocko wrote: > > I suppose that making mm always follow the threadgroup leader should > > be fine, right? > > That is the plan. Cool. > > While this wouldn't make any difference in the unified hierarchy, > > Just to make sure I understand. "wouldn't make any difference" because > the API is not backward compatible right? Hmm... because it's always per-process. If any thread is going, the whole process is going together. > > I think this would make more sense for traditional hierarchies. > > Yes I believe so. 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