From mboxrd@z Thu Jan 1 00:00:00 1970 From: Johannes Weiner Subject: Re: [RFC][PATCH 0/2] Android style loosening of cgroup attach permissions Date: Thu, 4 Jun 2015 14:36:58 -0400 Message-ID: <20150604183658.GA5682@cmpxchg.org> References: <1432179674-19154-1-git-send-email-john.stultz@linaro.org> <20150603055057.GE20091@mtj.duckdns.org> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: Sender: cgroups-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: John Stultz Cc: Tejun Heo , lkml , Li Zefan , Jonathan Corbet , cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Android Kernel Team , Rom Lemarchand , Colin Cross On Thu, Jun 04, 2015 at 10:11:17AM -0700, John Stultz wrote: > On Tue, Jun 2, 2015 at 10:50 PM, Tejun Heo wrote: > > memcg usage came up a while ago and there wasn't anything major which > > can't be achieved (usually better) by following more standard cgroup > > usage - changing knobs rather than moving tasks around. > > Do you have a pointer to that discussion or maybe even just a sense of > who was involved so I can trawl the list and better understand it? I wrote a lengthy explanation of why moving tasks between cgroups is problematic from a memcg view: https://lkml.org/lkml/2014/12/19/358 Rather than creating super-cgroups as configuration domains and using migration as a reconfiguration mechanism, it's much better to group tasks per app and reconfigure the groups themselves using specific presets for classes of apps, like foreground, background, audio. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932330AbbFDSh0 (ORCPT ); Thu, 4 Jun 2015 14:37:26 -0400 Received: from gum.cmpxchg.org ([85.214.110.215]:50604 "EHLO gum.cmpxchg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753726AbbFDShT (ORCPT ); Thu, 4 Jun 2015 14:37:19 -0400 Date: Thu, 4 Jun 2015 14:36:58 -0400 From: Johannes Weiner To: John Stultz Cc: Tejun Heo , lkml , Li Zefan , Jonathan Corbet , cgroups@vger.kernel.org, Android Kernel Team , Rom Lemarchand , Colin Cross Subject: Re: [RFC][PATCH 0/2] Android style loosening of cgroup attach permissions Message-ID: <20150604183658.GA5682@cmpxchg.org> References: <1432179674-19154-1-git-send-email-john.stultz@linaro.org> <20150603055057.GE20091@mtj.duckdns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jun 04, 2015 at 10:11:17AM -0700, John Stultz wrote: > On Tue, Jun 2, 2015 at 10:50 PM, Tejun Heo wrote: > > memcg usage came up a while ago and there wasn't anything major which > > can't be achieved (usually better) by following more standard cgroup > > usage - changing knobs rather than moving tasks around. > > Do you have a pointer to that discussion or maybe even just a sense of > who was involved so I can trawl the list and better understand it? I wrote a lengthy explanation of why moving tasks between cgroups is problematic from a memcg view: https://lkml.org/lkml/2014/12/19/358 Rather than creating super-cgroups as configuration domains and using migration as a reconfiguration mechanism, it's much better to group tasks per app and reconfigure the groups themselves using specific presets for classes of apps, like foreground, background, audio.