From: Juri Lelli <juri.lelli@arm.com>
To: Byungchul Park <byungchul.park@lge.com>
Cc: peterz@infradead.org, mingo@kernel.org,
linux-kernel@vger.kernel.org, juri.lelli@gmail.com,
kernel-team@lge.com, Steven Rostedt <rostedt@goodmis.org>,
Luca Abeni <luca.abeni@santannapisa.it>
Subject: Re: [PATCH] sched/deadline: Remove unnecessary condition in push_dl_task()
Date: Wed, 15 Feb 2017 10:47:49 +0000 [thread overview]
Message-ID: <20170215104749.GB1368@e106622-lin> (raw)
In-Reply-To: <1487135511-15817-1-git-send-email-byungchul.park@lge.com>
[+Steve, Luca]
Hi,
On 15/02/17 14:11, Byungchul Park wrote:
> Once pick_next_pushable_dl_task(rq) return a task, it guarantees that
> the task's cpu is rq->cpu, so task_cpu(next_task) is always rq->cpu if
> task == next_task. Remove a redundant condition and make code simpler.
>
> Signed-off-by: Byungchul Park <byungchul.park@lge.com>
> ---
> kernel/sched/deadline.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c
> index 27737f3..ad8d577 100644
> --- a/kernel/sched/deadline.c
> +++ b/kernel/sched/deadline.c
> @@ -1483,7 +1483,7 @@ static int push_dl_task(struct rq *rq)
> * then possible that next_task has migrated.
> */
> task = pick_next_pushable_dl_task(rq);
> - if (task_cpu(next_task) == rq->cpu && task == next_task) {
> + if (task == next_task) {
Seems a sensible optimization to me. Actually, we are doing the same for
rt.c; Steve, Peter, do you think we should optimize that as well?
Thanks,
- Juri
next prev parent reply other threads:[~2017-02-15 10:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 5:11 [PATCH] sched/deadline: Remove unnecessary condition in push_dl_task() Byungchul Park
2017-02-15 5:22 ` Byungchul Park
2017-02-15 10:47 ` Juri Lelli [this message]
2017-02-15 11:37 ` Peter Zijlstra
2017-02-15 14:25 ` Steven Rostedt
2017-02-15 14:45 ` Juri Lelli
2017-02-15 14:55 ` Steven Rostedt
2017-02-16 2:17 ` Byungchul Park
2017-02-16 2:31 ` Steven Rostedt
2017-02-16 2:33 ` Steven Rostedt
2017-02-16 2:41 ` Byungchul Park
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=20170215104749.GB1368@e106622-lin \
--to=juri.lelli@arm.com \
--cc=byungchul.park@lge.com \
--cc=juri.lelli@gmail.com \
--cc=kernel-team@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.abeni@santannapisa.it \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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