On Thu, 14 Oct 2010 11:59:55 +0200
Peter Zijlstra <peterz@infradead.org> wrote:

quoted text
> On Thu, 2010-10-14 at 18:50 +0900, KAMEZAWA Hiroyuki wrote:
> > On Thu, 14 Oct 2010 11:12:22 +0200
> > Peter Zijlstra <peterz@infradead.org> 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.
> 
Hmm, them, existing problem but this add a new pitfall.

What's your recomendation to make progess on this work ?

I think 1st step will be..
- explain the problem of priority inversion in cgroup+cfs documenation with
  !!CAUTION!!

I'm sorry I'm not sure there have been trials for fixing priority inversion
in the linux scheduler development.

Explaining my motivation, a user of this feature on my customer is virtual machine
rental service. So, some fuctionality as
"When vcpu holds spinlock in kernel, please don't sleep.." will be nice.
Is there patch already ?

Thanks,
-Kame










 

--
unsubscribe notice
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/