From: Hao Jia <jiahao.os@bytedance.com>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
dietmar.eggemann@arm.com, rostedt@goodmis.org,
bsegall@google.com, mgorman@suse.de, bristot@redhat.com,
vschneid@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [External] Re: [PATCH] sched/fair: Remove unused parameter idle of _nohz_idle_balance()
Date: Fri, 8 Jul 2022 18:31:56 +0800 [thread overview]
Message-ID: <1a9656a2-024e-497f-a0e6-3ec65910ab54@bytedance.com> (raw)
In-Reply-To: <CAKfTPtAb==WjCpmqOaVdwna6c+yxxskkRKwBKB7_EuJC9SrmJA@mail.gmail.com>
On 2022/7/7 Vincent Guittot wrote:
> On Thu, 7 Jul 2022 at 05:42, Hao Jia <jiahao.os@bytedance.com> wrote:
>>
>> Since commit 7a82e5f52a35 ("sched/fair: Merge for each idle cpu
>> loop of ILB") was merged. The parameter idle of _nohz_idle_balance()
>
> The description of the commit should be in a single line.
>
> commit 7a82e5f52a35 ("sched/fair: Merge for each idle cpu loop of ILB")
>
Thank you for your suggestion.
how about this?
Commit 7a82e5f52a35 ("sched/fair: Merge for each idle cpu loop of ILB")
has been merged. The parameter idle of _nohz_idle_balance()
is not used anymore so we can remove it.
Signed-off-by: Hao Jia <jiahao.os@bytedance.com>
Reviewed-by: Vincent Guittot <vincent.guittot@linaro.org>
>> is not used anymore so we can remove it.
>>
>> Signed-off-by: Hao Jia <jiahao.os@bytedance.com>
>
> Reviewed-by: Vincent Guittot <vincent.guittot@linaro.org>
>
>> ---
>> kernel/sched/fair.c | 7 +++----
>> 1 file changed, 3 insertions(+), 4 deletions(-)
>>
>> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
>> index 77b2048a9326..8d4be2a95e37 100644
>> --- a/kernel/sched/fair.c
>> +++ b/kernel/sched/fair.c
>> @@ -10682,8 +10682,7 @@ static bool update_nohz_stats(struct rq *rq)
>> * can be a simple update of blocked load or a complete load balance with
>> * tasks movement depending of flags.
>> */
>> -static void _nohz_idle_balance(struct rq *this_rq, unsigned int flags,
>> - enum cpu_idle_type idle)
>> +static void _nohz_idle_balance(struct rq *this_rq, unsigned int flags)
>> {
>> /* Earliest time when we have to do rebalance again */
>> unsigned long now = jiffies;
>> @@ -10798,7 +10797,7 @@ static bool nohz_idle_balance(struct rq *this_rq, enum cpu_idle_type idle)
>> if (idle != CPU_IDLE)
>> return false;
>>
>> - _nohz_idle_balance(this_rq, flags, idle);
>> + _nohz_idle_balance(this_rq, flags);
>>
>> return true;
>> }
>> @@ -10818,7 +10817,7 @@ void nohz_run_idle_balance(int cpu)
>> * (ie NOHZ_STATS_KICK set) and will do the same.
>> */
>> if ((flags == NOHZ_NEWILB_KICK) && !need_resched())
>> - _nohz_idle_balance(cpu_rq(cpu), NOHZ_STATS_KICK, CPU_IDLE);
>> + _nohz_idle_balance(cpu_rq(cpu), NOHZ_STATS_KICK);
>> }
>>
>> static void nohz_newidle_balance(struct rq *this_rq)
>> --
>> 2.32.0
>>
next prev parent reply other threads:[~2022-07-08 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 3:41 Hao Jia
2022-07-07 14:17 ` Vincent Guittot
2022-07-08 10:31 ` Hao Jia [this message]
2022-07-08 12:50 ` [External] " Vincent Guittot
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=1a9656a2-024e-497f-a0e6-3ec65910ab54@bytedance.com \
--to=jiahao.os@bytedance.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.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 \
--cc=vschneid@redhat.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
all inboxes | Powered by JetHome®