Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755559AbcDMTPm (ORCPT ); Wed, 13 Apr 2016 15:15:42 -0400 Received: from mail-wm0-f51.google.com ([74.125.82.51]:37390 "EHLO mail-wm0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752348AbcDMTPj (ORCPT ); Wed, 13 Apr 2016 15:15:39 -0400 Message-ID: <1460574934.3775.77.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 Cc: Peter Zijlstra , 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: Wed, 13 Apr 2016 21:15:34 +0200 In-Reply-To: <20160413155952.GU24661@htj.duckdns.org> References: <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> <20160409133917.GV3448@twins.programming.kicks-ass.net> <20160412222915.GT24661@htj.duckdns.org> <1460533381.3780.191.camel@gmail.com> <20160413155952.GU24661@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: 645 Lines: 16 On Wed, 2016-04-13 at 11:59 -0400, Tejun Heo wrote: > Are you saying that you're aware that google or another big outfit is > making active use of internal tasks competing against sibling cgroups > for proportional CPU distribution? If so, can you please be more > specific? What I'm aware of is a big outfit that moves thread pool workers in/out of a large number of cpu/cpuacct cgroups. What all a worker thread may spawn in a cgroup, or find already there upon arrival and thus compete with I do not know. I'm baffled by why anyone would care which entity competes with which other entity. An entity is an entity is an entity. -Mike