From: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
To: Wanpeng Li <wanpeng.li@linux.intel.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Jason Low <jason.low2@hp.com>,
Preeti U Murthy <preeti@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] sched/fair: fix update the nohz.next_balance even if we haven't done any load balance
Date: Fri, 27 Mar 2015 16:58:23 +0530 [thread overview]
Message-ID: <20150327112823.GC6895@linux.vnet.ibm.com> (raw)
In-Reply-To: <1427442750-8112-1-git-send-email-wanpeng.li@linux.intel.com>
* Wanpeng Li <wanpeng.li@linux.intel.com> [2015-03-27 15:52:30]:
> As Srikar pointed out (https://lkml.org/lkml/2015/3/27/26):
>
> | With the current code when the ilb cpus are not free:
> | - We would be updating the nohz.next_balance even through we havent done
> | any load balance.
> | - We might iterate thro the nohz.idle_cpus_mask()s to find balance_cpus.
>
> This patch fix it by adding need_resched check with the idle check, and
> keep the need_resched check in for loop to catch ilb get busy.
>
> Suggested-by: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
> Reviewed-by: Jason Low <jason.low2@hp.com>
> Signed-off-by: Wanpeng Li <wanpeng.li@linux.intel.com>
Looks good to me.
Reviewed-by: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
> ---
> kernel/sched/fair.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index 0576ce0..788e42f 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -7638,7 +7638,7 @@ static void nohz_idle_balance(struct rq *this_rq, enum cpu_idle_type idle)
> struct rq *rq;
> int balance_cpu;
>
> - if (idle != CPU_IDLE ||
> + if (idle != CPU_IDLE || need_resched() ||
> !test_bit(NOHZ_BALANCE_KICK, nohz_flags(this_cpu)))
> goto end;
>
> --
> 1.9.1
>
--
Thanks and Regards
Srikar Dronamraju
prev parent reply other threads:[~2015-03-27 11:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 7:52 Wanpeng Li
2015-03-27 11:28 ` Srikar Dronamraju [this message]
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=20150327112823.GC6895@linux.vnet.ibm.com \
--to=srikar@linux.vnet.ibm.com \
--cc=jason.low2@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=preeti@linux.vnet.ibm.com \
--cc=wanpeng.li@linux.intel.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
Powered by JetHome