From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Yong Zhang <yong.zhang0@gmail.com>
Cc: Lin Ming <ming.m.lin@intel.com>, "mingo@elte.hu" <mingo@elte.hu>,
lkml <linux-kernel@vger.kernel.org>,
Mike Galbraith <efault@gmx.de>
Subject: Re: [PATCH] sched: Remove WAKEUP_PREEMPT feature check in entity_tick
Date: Fri, 29 Jul 2011 10:20:50 +0200 [thread overview]
Message-ID: <1311927650.5890.217.camel@twins> (raw)
In-Reply-To: <20110729081800.GA12106@zhy>
On Fri, 2011-07-29 at 16:18 +0800, Yong Zhang wrote:
> > Nah, if there is 1 runnable task it will always run, preemption simply
> > doesn't matter. There's nothing to preempt it with.
>
> Hmmm, so the newly waked task could be scheduled a little later.
> That means schedule tick judge everything.
Oh, are you referring to the case where a task gets woken on an idle
remote cpu?
next prev parent reply other threads:[~2011-07-29 8:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 9:43 [PATCH] sched: Remove WAKEUP_PREEMPT feature check in entity_tick Lin Ming
2011-07-29 6:21 ` Yong Zhang
2011-07-29 6:24 ` Yong Zhang
2011-07-29 6:49 ` Lin Ming
2011-07-29 7:03 ` Yong Zhang
2011-07-29 7:36 ` Lin Ming
2011-07-29 7:46 ` Yong Zhang
2011-07-29 7:56 ` Lin Ming
2011-07-29 7:56 ` Peter Zijlstra
2011-07-29 8:18 ` Yong Zhang
2011-07-29 8:20 ` Peter Zijlstra [this message]
2011-07-29 8:44 ` Lin Ming
2011-07-29 8:46 ` Yong Zhang
2011-07-29 11:45 ` Peter Zijlstra
2011-08-01 1:33 ` Yong Zhang
2011-07-29 8:20 ` [RFC PATCH] sched: Kill WAKEUP_PREEMPT Yong Zhang
2011-07-29 8:30 ` Lin Ming
2011-07-29 8:32 ` Lin Ming
2011-08-14 15:57 ` [tip:sched/core] " tip-bot for Yong Zhang
2011-07-29 9:04 ` [PATCH] sched: Remove WAKEUP_PREEMPT feature check in entity_tick 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=1311927650.5890.217.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=mingo@elte.hu \
--cc=yong.zhang0@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