From: Ingo Molnar <mingo@kernel.org>
To: Wen Yang <wen.yang99@zte.com.cn>
Cc: mingo@redhat.com, peterz@infradead.org,
linux-kernel@vger.kernel.org, jiang.biao2@zte.com.cn,
zhong.weidong@zte.com.cn
Subject: Re: [PATCH] sched/rt: Make update_curr_rt() more accurate
Date: Mon, 5 Feb 2018 11:57:08 +0100 [thread overview]
Message-ID: <20180205105708.upjcsok3zbk5zxlk@gmail.com> (raw)
In-Reply-To: <1517800721-42092-1-git-send-email-wen.yang99@zte.com.cn>
* Wen Yang <wen.yang99@zte.com.cn> wrote:
> rq->clock_task may be updated between the two calls of
> rq_clock_task() in update_curr_rt(). Calling rq_clock_task() only
> once makes it more accurate and efficient, taking update_curr() as
> reference.
>
> Signed-off-by: Wen Yang <wen.yang99@zte.com.cn>
> Reviewed-by: Jiang Biao <jiang.biao2@zte.com.cn>
> ---
> kernel/sched/rt.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/sched/rt.c b/kernel/sched/rt.c
> index 4056c19..d6d2a65 100644
> --- a/kernel/sched/rt.c
> +++ b/kernel/sched/rt.c
> @@ -950,12 +950,13 @@ static void update_curr_rt(struct rq *rq)
> {
> struct task_struct *curr = rq->curr;
> struct sched_rt_entity *rt_se = &curr->rt;
> + u64 now = rq_clock_task(rq);
> u64 delta_exec;
>
> if (curr->sched_class != &rt_sched_class)
> return;
>
> - delta_exec = rq_clock_task(rq) - curr->se.exec_start;
> + delta_exec = now - curr->se.exec_start;
Small nit: shouldn't we calculate 'now' after the return?
OTOH that 'return' should only be triggered statistically AFAICS, i.e. very
rarely.
Thanks,
Ingo
next prev parent reply other threads:[~2018-02-05 10:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 3:18 Wen Yang
2018-02-05 10:30 ` Peter Zijlstra
2018-02-05 10:31 ` Peter Zijlstra
2018-02-05 10:57 ` Ingo Molnar [this message]
2018-02-06 11:55 ` [tip:sched/urgent] " tip-bot for Wen Yang
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=20180205105708.upjcsok3zbk5zxlk@gmail.com \
--to=mingo@kernel.org \
--cc=jiang.biao2@zte.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=wen.yang99@zte.com.cn \
--cc=zhong.weidong@zte.com.cn \
/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
Powered by JetHome