From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Yogesh Ahire <yogesh02061983@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sched_yield() call on Linux Kernel 2.6.39 is not behaving correct
Date: Sat, 10 Jan 2015 08:37:55 +0100 [thread overview]
Message-ID: <1420875475.5283.135.camel@marge.simpson.net> (raw)
In-Reply-To: <CAH86sKJnx1wgtkZ-S0QHcRf4dXvSsVoB4U66Yf2vLpruuNeYNA@mail.gmail.com>
On Fri, 2015-01-09 at 11:24 -0800, Yogesh Ahire wrote:
> Thank you Mike. I didn't get what you mean by saying "its gona try to
> yield for one hell of a long time before it succeeds".
Look at vruntimes. Equalizing same is what the scheduler does for a
living, it does so by giving the CPU to the runnable task with the
lowest vruntime. Exec time is scaled by load to become vruntime, but
this vruntime delta is so large you may as well just call it infinity.
-Mike
prev parent reply other threads:[~2015-01-10 7:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 21:30 sched_yield() call on Linux Kernel 2.6.39 is not behaving correct Yogesh Ahire
2015-01-08 5:26 ` Mike Galbraith
2015-01-08 15:00 ` Yogesh Ahire
2015-01-09 3:14 ` Mike Galbraith
2015-01-09 19:24 ` Yogesh Ahire
2015-01-10 7:37 ` Mike Galbraith [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1420875475.5283.135.camel@marge.simpson.net \
--to=umgwanakikbuti@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yogesh02061983@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.