On 12/17/2010 09:51 PM, Mike Galbraith wrote:
quoted text
> On Fri, 2010-12-17 at 17:09 +0200, Avi Kivity wrote:
> >  On 12/17/2010 08:56 AM, Mike Galbraith wrote:
> >  >  >   Surely that makes it a reasonable idea to call yield, and
> >  >  >   get one of the other tasks on the current CPU running for
> >  >  >   a bit?
> >  >
> >  >  There's nothing wrong with trying to give up the cpu.  It's the concept
> >  >  of a cross cpu yield_to() that I find mighty strange.
> >
> >  What's so strange about it?  From a high level there are N runnable
> >  tasks contending for M cpus.  If task X really needs task Y to run, what
> >  does it matter if task Y last ran on the same cpu as task X or not?
>
> Task X wants control of when runnable task Y gets the cpu.  Task X
> clearly wants to be the scheduler.  This isn't about _yielding_ diddly
> spit, it's about individual tasks wanting to make scheduling decisions,
> so calling it a yield is high grade horse-pookey.  You're trying to give
> the scheduler a hint, the stronger that hint, the happier you'll be.

Please suggest a better name then.

quoted text
> I can see the problem, and I'm not trying to be Mr. Negative here, I'm
> only trying to point out problems I see with what's been proposed.
>
> If the yielding task had a concrete fee he could pay, that would be
> fine, but he does not.

It does.  The yielding task is entitled to its fair share of the cpu, as 
modified by priority and group scheduling.  The yielding task is willing 
to give up some of this cpu, in return for increasing another task's 
share.  Other tasks would not be negatively affected by this.

quoted text
> If he did have something, how often do you think it should be possible
> for task X to bribe the scheduler into selecting task Y?

In extreme cases, very often.  Say 100KHz.

quoted text
> Will his
> pockets be deep enough to actually solve the problem?  Once he's
> yielded, he's out of the picture for a while if he really gave anything
> up.

Unless the other task donates some cpu share back.  This is exactly what 
will happen in those extreme cases.

quoted text
> What happens to donated entitlement when the recipient goes to
> sleep?

Nothing.

quoted text
> If you try to give it back, what happens if the donor exited?

It's lost, too bad.

quoted text
> Where did the entitlement come from if task A running alone on cpu A
> tosses some entitlement over the fence to his pal task B on cpu B.. and
> keeps on trucking on cpu A?  Where does that leave task C, B's
> competition?

Eventually C would replace A, since its share will be exhausted.  If C 
is pinned... good question.  How does fairness work with pinned tasks?

quoted text
> >  Do I correctly read between the lines that CFS maintains complete
> >  fairness only on a cpu, but not globally?
>
> Nothing between the lines about it.  There are N individual engines,
> coupled via load balancing.

Is this not seen as a major deficiency?

I can understand intra-cpu scheduling decisions at 300 Hz and inter-cpu 
decisions at 10 Hz (or even lower, with some intermediate rate for 
intra-socket scheduling).  But this looks like a major deviation from 
fairness - instead of 33%/33%/33% you get 50%/25%/25% depending on 
random placement.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.

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