Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754148AbaGOPV4 (ORCPT ); Tue, 15 Jul 2014 11:21:56 -0400 Received: from mail-qc0-f179.google.com ([209.85.216.179]:57303 "EHLO mail-qc0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751478AbaGOPVx (ORCPT ); Tue, 15 Jul 2014 11:21:53 -0400 Date: Tue, 15 Jul 2014 11:21:49 -0400 From: Tejun Heo To: Peter Zijlstra Cc: Tim Chen , Herbert Xu , "H. Peter Anvin" , "David S.Miller" , Ingo Molnar , Chandramouli Narayanan , Vinodh Gopal , James Guilford , Wajdi Feghali , Jussi Kivilinna , linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v4 6/7] sched: add function nr_running_cpu to expose number of tasks running on cpu Message-ID: <20140715152149.GC19570@htj.dyndns.org> References: <1405110784.2970.655.camel@schen9-DESK> <20140714101611.GS9918@twins.programming.kicks-ass.net> <1405354214.2970.663.camel@schen9-DESK> <20140714161432.GC9918@twins.programming.kicks-ass.net> <1405357534.2970.701.camel@schen9-DESK> <20140714181738.GI9918@twins.programming.kicks-ass.net> <1405364908.2970.729.camel@schen9-DESK> <20140714191504.GO9918@twins.programming.kicks-ass.net> <20140715133627.GS3588@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140715133627.GS3588@twins.programming.kicks-ass.net> 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 Tue, Jul 15, 2014 at 03:36:27PM +0200, Peter Zijlstra wrote: > So, just to expand on this, we're already getting 'bug' reports because > worker threads are not cgroup aware. If work gets generated inside some > cgroup, the worker doesn't care and runs the worker thread wherever > (typically the root cgroup). > > This means that the 'work' escapes the cgroup confines and creates > resource inversion etc. The same is of course true for nice and RT > priorities. > > TJ, are you aware of this and/or given it any throught? Yeap, I'm aware of the issue but haven't read any actual bug reports yet. Can you point me to the reports? Given that worker pool management is dynamic, spawning separate pools for individual cgroups on-demand should be doable. Haven't been able to decide how much we should be willing to pay in terms of complexity yet. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/