From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Hao Jia <jiahao.os@bytedance.com>,
mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, rostedt@goodmis.org,
bsegall@google.com, mgorman@suse.de, bristot@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] sched/dl: Remove some comments and adjust code in push_dl_task
Date: Mon, 25 Apr 2022 18:21:20 +0200 [thread overview]
Message-ID: <cfab5ffc-af96-8368-0aae-927a6be65472@arm.com> (raw)
In-Reply-To: <20220422090944.52618-3-jiahao.os@bytedance.com>
On 22/04/2022 11:09, Hao Jia wrote:
Nitpick: I would change the message slightly into something like:
sched/deadline: Remove superfluous rq clock update in push_dl_task()
> The change to call update_rq_clock() before activate_task()
> commit 840d719604b0 ("sched/deadline: Update rq_clock of later_rq
> when pushing a task") is no longer needed since commit f4904815f97a
> ("sched/deadline: Fix double accounting of rq/running bw in push & pull")
> removed the add_running_bw() before the activate_task().
>
> So we remove some comments that are no longer needed and update
> rq clock in activate_task().
>
> Signed-off-by: Hao Jia <jiahao.os@bytedance.com>
> ---
> kernel/sched/deadline.c | 8 +-------
> 1 file changed, 1 insertion(+), 7 deletions(-)
>
> diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c
> index fb4255ae0b2c..8eb694ed7ac1 100644
> --- a/kernel/sched/deadline.c
> +++ b/kernel/sched/deadline.c
> @@ -2319,13 +2319,7 @@ static int push_dl_task(struct rq *rq)
>
> deactivate_task(rq, next_task, 0);
> set_task_cpu(next_task, later_rq->cpu);
> -
> - /*
> - * Update the later_rq clock here, because the clock is used
> - * by the cpufreq_update_util() inside __add_running_bw().
> - */
> - update_rq_clock(later_rq);
> - activate_task(later_rq, next_task, ENQUEUE_NOCLOCK);
> + activate_task(later_rq, next_task, 0);
> ret = 1;
>
> resched_curr(later_rq);
Reviewed-by: Dietmar Eggemann <dietmar.eggemann@arm.com>
next prev parent reply other threads:[~2022-04-25 16:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 9:09 [PATCH v2 0/2] Avoid obvious double update_rq_clock warning Hao Jia
2022-04-22 9:09 ` [PATCH v2 1/2] sched/core: " Hao Jia
2022-04-25 15:37 ` Dietmar Eggemann
2022-04-26 7:57 ` [External] " Hao Jia
2022-04-22 9:09 ` [PATCH v2 2/2] sched/dl: Remove some comments and adjust code in push_dl_task Hao Jia
2022-04-25 16:21 ` Dietmar Eggemann [this message]
2022-04-26 8:01 ` [External] " Hao Jia
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=cfab5ffc-af96-8368-0aae-927a6be65472@arm.com \
--to=dietmar.eggemann@arm.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=jiahao.os@bytedance.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.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®