From: Peter Zijlstra <peterz@infradead.org>
To: pang.xunlei@zte.com.cn
Cc: Juri Lelli <juri.lelli@gmail.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Xunlei Pang <pang.xunlei@linaro.org>,
Steven Rostedt <rostedt@goodmis.org>,
Xunlei Pang <xlpang@126.com>
Subject: Re: [PATCH v3 1/4] sched/rt: Check to push the task away after its affinity was changed
Date: Sat, 30 May 2015 12:54:23 +0200 [thread overview]
Message-ID: <1432983263.11346.15.camel@twins> (raw)
In-Reply-To: <20150530082035.GL19282@twins.programming.kicks-ass.net>
On Sat, 2015-05-30 at 10:20 +0200, Peter Zijlstra wrote:
> Makes me like the thing even less though..
Steven, why do we normally push on schedule()? Would not the natural
location be where we add to pushable_tasks?
Which would be here in set_cpus_allowed() and wakeups. schedule() seems
like a second best location.
next prev parent reply other threads:[~2015-05-30 10:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 14:46 [PATCH v3 1/4] sched/rt: Check to push the task away after its affinity was changed Xunlei Pang
2015-05-12 14:46 ` [PATCH v3 2/4] sched/deadline: " Xunlei Pang
2015-05-12 14:46 ` [PATCH v3 3/4] sched/rt: Remove redundant conditions from task_woken_rt() Xunlei Pang
2015-05-12 14:46 ` [PATCH v3 4/4] sched/deadline: Remove redundant conditions from task_woken_dl() Xunlei Pang
2015-05-29 13:16 ` [PATCH v3 1/4] sched/rt: Check to push the task away after its affinity was changed Peter Zijlstra
[not found] ` <OF8BB81194.1A32A464-ON48257E54.004C068A-48257E54.004D51E2@zte.com.cn>
2015-05-30 8:20 ` Peter Zijlstra
2015-05-30 10:54 ` Peter Zijlstra [this message]
2015-05-30 16:30 ` Steven Rostedt
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=1432983263.11346.15.camel@twins \
--to=peterz@infradead.org \
--cc=juri.lelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pang.xunlei@linaro.org \
--cc=pang.xunlei@zte.com.cn \
--cc=rostedt@goodmis.org \
--cc=xlpang@126.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