From: Peter Zijlstra <peterz@infradead.org>
To: stephan.baerwolf@tu-ilmenau.de
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
ncrao@google.com
Subject: Re: sched: fix/optimise some issues
Date: Wed, 20 Jul 2011 21:11:40 +0200 [thread overview]
Message-ID: <1311189100.29152.75.camel@twins> (raw)
In-Reply-To: <4E26DB41.9070002@tu-ilmenau.de>
On Wed, 2011-07-20 at 15:42 +0200, Stephan Bärwolf wrote:
>
> The function "check_preempt_wakeup" (kernel/sched_fair.c:1885)
> will preempt idle-task (for non-idle task), even if WAKEUP_PREEMPT
> is not featured (because of a too late checking the feature).
> This patches moves the checking of WAKEUP_PREEMT in front of
> idle-preemtion.
That's actually on purpose, the WAKE_PREEMPT feature is supposed to only
affect preemption between SCHED_OTHER tasks.
next prev parent reply other threads:[~2011-07-20 19:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 13:42 sched: fix/optimise some issues Stephan Bärwolf
2011-07-20 19:11 ` Peter Zijlstra
2011-07-21 1:00 ` Mike Galbraith
2011-07-20 19:11 ` Peter Zijlstra
2011-07-20 19:11 ` Peter Zijlstra [this message]
2011-07-21 15:08 ` Peter Zijlstra
2011-07-21 16:36 ` Stephan Bärwolf
2011-07-21 16:32 ` Peter Zijlstra
2011-07-21 16:43 ` Peter Zijlstra
2011-07-21 16:51 ` Peter Zijlstra
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=1311189100.29152.75.camel@twins \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=ncrao@google.com \
--cc=stephan.baerwolf@tu-ilmenau.de \
/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