From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755349Ab0JNKA3 (ORCPT ); Thu, 14 Oct 2010 06:00:29 -0400 Received: from canuck.infradead.org ([134.117.69.58]:53208 "EHLO canuck.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753498Ab0JNKA2 convert rfc822-to-8bit (ORCPT ); Thu, 14 Oct 2010 06:00:28 -0400 Subject: Re: [PATCH v3 3/7] sched: throttle cfs_rq entities which exceed their local quota From: Peter Zijlstra To: KAMEZAWA Hiroyuki Cc: bharata@linux.vnet.ibm.com, linux-kernel@vger.kernel.org, Dhaval Giani , Balbir Singh , Vaidyanathan Srinivasan , Srivatsa Vaddagiri , Kamalesh Babulal , Ingo Molnar , Pavel Emelyanov , Herbert Poetzl , Avi Kivity , Chris Friesen , Paul Menage , Mike Waychison , Paul Turner , Nikhil Rao In-Reply-To: <20101014185002.6ecb2bf5.kamezawa.hiroyu@jp.fujitsu.com> References: <20101012074910.GA9893@in.ibm.com> <20101012075202.GD9893@in.ibm.com> <20101013153421.b38a5c6f.kamezawa.hiroyu@jp.fujitsu.com> <1287047542.29097.169.camel@twins> <20101014185002.6ecb2bf5.kamezawa.hiroyu@jp.fujitsu.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT Date: Thu, 14 Oct 2010 11:59:55 +0200 Message-ID: <1287050395.29097.176.camel@twins> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2010-10-14 at 18:50 +0900, KAMEZAWA Hiroyuki wrote: > On Thu, 14 Oct 2010 11:12:22 +0200 > Peter Zijlstra wrote: > > > On Wed, 2010-10-13 at 15:34 +0900, KAMEZAWA Hiroyuki wrote: > > > cpu.share and bandwidth control can't be used simultaneously or... > > > is this fair ? I'm not familiar with scheduler but this allows boost this tg. > > > Could you add a brief documentaion of a spec/feature. in the next post ? > > > > Like explained, shares control the proportional distribution of time > > between groups, bandwidth puts a limit on how much time a group can > > take. It can cause a group to receive less than its fair share, but > > never more. > > > > There is, however, a problem with all this, and that is that all this > > explicit idling of tasks can lead to a form of priority inversion. > > Regular preemptive scheduling already suffers from this, but explicitly > > idling tasks exacerbates the situation. > > > > You basically get to add the longest induced idle time to all your lock > > hold times. > > > > What is the user-visible difference of the problem between > 1) limit share to be very small. > 2) use throttole. > > If share is used, lock-hodler's priority is boosted ? No, both lead to the same problem, its just that this adds another dimension to it.. and I'm fairly sure people won't realise this until it bites them in the ass.