From: Mike Galbraith <efault@gmx.de>
To: Lin Ming <ming.m.lin@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@elte.hu>,
"Zhang, Yanmin" <yanmin_zhang@linux.intel.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: netperf ~50% regression with 2.6.33-rc1, bisect to 1b9508f
Date: Mon, 25 Jan 2010 12:35:42 +0100 [thread overview]
Message-ID: <1264419342.5888.42.camel@marge.simson.net> (raw)
In-Reply-To: <1264413826.3642.88.camel@minggr.sh.intel.com>
On Mon, 2010-01-25 at 18:03 +0800, Lin Ming wrote:
> With above commit, the idle balance was rate limited, so CPU 15(server,
> waiting data from client) is idle at most time.
>
> CPU0(client) executes as below,
>
> try_to_wake_up
> check_preempt_curr_idle
> resched_task
> smp_send_reschedule
>
> This causes a lot of rescheduling IPI.
>
> This commit can't be reverted due to conflict, so I just add below code
> to disable "Rate-limit newidle" and the performance was recovered.
>
> diff --git a/kernel/sched.c b/kernel/sched.c
> index 18cceee..588fdef 100644
> --- a/kernel/sched.c
> +++ b/kernel/sched.c
> @@ -4421,9 +4421,6 @@ static void idle_balance(int this_cpu, struct rq *this_rq)
>
> this_rq->idle_stamp = this_rq->clock;
>
> - if (this_rq->avg_idle < sysctl_sched_migration_cost)
> - return;
> -
> for_each_domain(this_cpu, sd) {
> unsigned long interval;
>
Heh, so you should see the same thing with newidle disabled, as it was
in .31 and many kernels prior. Do you?
So. Rummaging around doing absolutely _nothing_ useful, there being
zero movable tasks in this load, prevents us switching to the idle
thread before the scheduling task is requeued. Oh joy.
Hm.... <imagines Peter's reaction to a busy wait> :) OTOH, that's what
it's _doing_ with above patch.
-Mike
next prev parent reply other threads:[~2010-01-25 11:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 10:03 netperf ~50% regression with 2.6.33-rc1, bisect to 1b9508f Lin Ming
2010-01-25 11:35 ` Mike Galbraith [this message]
2010-01-25 11:45 ` Mike Galbraith
2010-01-26 9:03 ` Lin Ming
2010-01-25 14:03 ` Peter Zijlstra
2010-01-25 14:19 ` Mike Galbraith
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=1264419342.5888.42.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=yanmin_zhang@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