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: Fri, 09 Jan 2015 04:14:40 +0100 [thread overview]
Message-ID: <1420773280.5340.16.camel@marge.simpson.net> (raw)
In-Reply-To: <CAH86sKJJWACmjC0VfF4AHEvsLQ42T81JOYseykzrEB=tVfZQDA@mail.gmail.com>
On Thu, 2015-01-08 at 10:00 -0500, Yogesh Ahire wrote:
> Thank you Mike. But I can see there are tasks with same priority and
> are runnable waiting for CPU, following is the output of
> /proc/sched_debug where you can see that the task "symphonyapp"
> continuously calls sched_yield() but there are other tasks which are
> ready to run are not getting CPU and are queued back.
Something terminally bad happened. With that tasks vruntime (tree-key),
it's gonna try to yield for one hell of a long time before it succeeds.
-Mike
next prev parent reply other threads:[~2015-01-09 3:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 21:30 Yogesh Ahire
2015-01-08 5:26 ` Mike Galbraith
2015-01-08 15:00 ` Yogesh Ahire
2015-01-09 3:14 ` Mike Galbraith [this message]
2015-01-09 19:24 ` Yogesh Ahire
2015-01-10 7:37 ` Mike Galbraith
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=1420773280.5340.16.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®