Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752513AbcDIGQv (ORCPT ); Sat, 9 Apr 2016 02:16:51 -0400 Received: from mail-wm0-f48.google.com ([74.125.82.48]:33054 "EHLO mail-wm0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750897AbcDIGQs (ORCPT ); Sat, 9 Apr 2016 02:16:48 -0400 Message-ID: <1460182603.3765.155.camel@gmail.com> Subject: Re: [PATCHSET RFC cgroup/for-4.6] cgroup, sched: implement resource group and PRIO_RGRP From: Mike Galbraith To: Tejun Heo , Peter Zijlstra Cc: Johannes Weiner , torvalds@linux-foundation.org, akpm@linux-foundation.org, mingo@redhat.com, lizefan@huawei.com, pjt@google.com, linux-kernel@vger.kernel.org, cgroups@vger.kernel.org, linux-api@vger.kernel.org, kernel-team@fb.com Date: Sat, 09 Apr 2016 08:16:43 +0200 In-Reply-To: <20160408201135.GO24661@htj.duckdns.org> References: <1457710888-31182-1-git-send-email-tj@kernel.org> <20160314113013.GM6344@twins.programming.kicks-ass.net> <20160406155830.GI24661@htj.duckdns.org> <20160407064549.GH3430@twins.programming.kicks-ass.net> <20160407073547.GA12560@cmpxchg.org> <20160407080833.GK3430@twins.programming.kicks-ass.net> <20160407194555.GI7822@mtj.duckdns.org> <20160407202542.GD3448@twins.programming.kicks-ass.net> <20160408201135.GO24661@htj.duckdns.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.16.5 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1128 Lines: 26 On Fri, 2016-04-08 at 16:11 -0400, Tejun Heo wrote: > > That's just plain broken... That is not how a proportional weight based > > hierarchical controller works. > > That's a strong statement. When the hierarchy is composed of > equivalent objects as in CPU, not distinguishing internal and leaf > nodes would be a more natural way to organize; however... You almost said it yourself, you want to make the natural organization of cpu, cpuacct and cpuset controllers a prohibited organization. There is no "however..." that can possibly justify that. It's akin to mandating: henceforth "horse" shall be spelled "cow", riders thereof shall teach their "cow" the proper enunciation of "moo". It's silly. Like it or not, these controllers have thread encoded in their DNA, it's an integral part of what they are, and how real users in the real world use them. No rationalization will change that cold hard fact. Make an "Aunt Tilly" button for those incapable of comprehending the complexities if you will, but please don't make cgroups so rigid and idiot proof that only idiots (hi system thing) can use it. -Mike