From: Peter Zijlstra <peterz@infradead.org>
To: George McCollister <george.mccollister@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched: fix double normalization of vruntime
Date: Wed, 26 Feb 2014 14:28:52 +0100 [thread overview]
Message-ID: <20140226132852.GB30956@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1392767811-28916-1-git-send-email-george.mccollister@gmail.com>
On Tue, Feb 18, 2014 at 05:56:51PM -0600, George McCollister wrote:
> dequeue_entity() is called when p->on_rq and sets se->on_rq = 0
> which appears to guarentee that the !se->on_rq condition is met.
> If the task has done set_current_state(TASK_INTERRUPTIBLE) without
> schedule() the second condition will be met and vruntime will be
> incorrectly adjusted twice.
>
> In certain cases this can result in the task's vruntime never increasing
> past the vruntime of other tasks on the CFS' run queue, starving them of
> CPU time.
>
> This patch changes switched_from_fair() to use !p->on_rq instead of
> !se->on_rq.
>
> I'm able to cause a task with a priority of 120 to starve all other
> tasks with the same priority on an ARM platform running 3.2.51-rt72
> PREEMPT RT by writing one character at time to a serial tty (16550 UART)
> in a tight loop. I'm also able to verify making this change corrects the
> problem on that platform and kernel version.
>
> I haven't and not sure I will have an opportunity to get a newer kernel
> version running on the platform mentioned above and have yet to
> reproduce the problem on another platform.
Yes, I think you're quite right. Another way to look at this is that
p->on_rq is the one matching p->state.
Can I have (or add) your Signed-off-by for this patch?
next prev parent reply other threads:[~2014-02-26 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 23:56 George McCollister
2014-02-26 13:28 ` Peter Zijlstra [this message]
2014-02-26 18:59 ` George McCollister
2014-02-27 13:31 ` [tip:sched/urgent] sched: Fix " tip-bot for George McCollister
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=20140226132852.GB30956@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=george.mccollister@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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®