From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: vincent.donnefort@arm.com, mingo@redhat.com, peterz@infradead.org
Cc: linux-kernel@vger.kernel.org, valentin.schneider@arm.com,
Vincent Guittot <vincent.guittot@linaro.org>
Subject: Re: [PATCH] sched: Remove unused last_load_update_tick rq member
Date: Fri, 20 Mar 2020 14:44:55 +0100 [thread overview]
Message-ID: <e400d0b1-173f-bcfd-40c0-2e473e14e7ae@arm.com> (raw)
In-Reply-To: <1584710495-308969-1-git-send-email-vincent.donnefort@arm.com>
+ Vincent Guittot
On 20.03.20 14:21, vincent.donnefort@arm.com wrote:
> From: Vincent Donnefort <vincent.donnefort@arm.com>
>
> The commit 5e83eafbfd3b ("sched/fair: Remove the rq->cpu_load[] update
> code") eliminated the use case for rq->last_load_update_tick. Removing
> it.
>
> Signed-off-by: Vincent Donnefort <vincent.donnefort@arm.com>
>
> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> index 1a9983d..c41ee26 100644
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -6685,7 +6685,6 @@ void __init sched_init(void)
>
> rq_attach_root(rq, &def_root_domain);
> #ifdef CONFIG_NO_HZ_COMMON
> - rq->last_load_update_tick = jiffies;
> rq->last_blocked_load_update_tick = jiffies;
> atomic_set(&rq->nohz_flags, 0);
> #endif
> diff --git a/kernel/sched/sched.h b/kernel/sched/sched.h
> index 9ea6478..6e14fad 100644
> --- a/kernel/sched/sched.h
> +++ b/kernel/sched/sched.h
> @@ -860,7 +860,6 @@ struct rq {
> #endif
> #ifdef CONFIG_NO_HZ_COMMON
> #ifdef CONFIG_SMP
> - unsigned long last_load_update_tick;
> unsigned long last_blocked_load_update_tick;
> unsigned int has_blocked_load;
> #endif /* CONFIG_SMP */
Reviewed-by: Dietmar Eggemann <dietmar.eggemann@arm.com>
next prev parent reply other threads:[~2020-03-20 13:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 13:21 vincent.donnefort
2020-03-20 13:44 ` Dietmar Eggemann [this message]
2020-03-20 13:57 ` Vincent Guittot
2020-04-08 12:20 ` [tip: sched/urgent] sched/core: Remove unused rq::last_load_update_tick tip-bot2 for Vincent Donnefort
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=e400d0b1-173f-bcfd-40c0-2e473e14e7ae@arm.com \
--to=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=valentin.schneider@arm.com \
--cc=vincent.donnefort@arm.com \
--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®