From: David Ahern <david.ahern@oracle.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Mike Galbraith <efault@gmx.de>, Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: NMI watchdog triggering during load_balance
Date: Fri, 06 Mar 2015 08:10:57 -0700 [thread overview]
Message-ID: <54F9C381.3000305@oracle.com> (raw)
In-Reply-To: <20150306090731.GY21418@twins.programming.kicks-ass.net>
On 3/6/15 2:07 AM, Peter Zijlstra wrote:
> On Thu, Mar 05, 2015 at 09:05:28PM -0700, David Ahern wrote:
>> Since each domain is a superset of the lower one each pass through
>> load_balance regularly repeats the processing of the previous domain (e.g.,
>> NODE domain repeats the cpus in the CPU domain). Then multiplying that
>> across 1024 cpus and it seems like a of duplication.
>
> It is, _but_ each domain has an interval, bigger domains _should_ load
> balance at a bigger interval (iow lower frequency), and all this is
> lockless data gathering, so reusing stuff from the previous round could
> be quite stale indeed.
>
Yes and I have twiddled the intervals. The defaults for min_interval and
max_interval (msec):
SMT 1 2
MC 1 4
CPU 1 4
NODE 8 32
Increasing those values (e.g. moving NODE to 50 and 100) drops idle time
cpu usage but does not solve the fundamental problem -- under load the
balancing of domains seems to be lining up and the system comes to a
halt in load balancing frenzy.
David
next prev parent reply other threads:[~2015-03-06 15:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 4:05 David Ahern
2015-03-06 4:52 ` Mike Galbraith
2015-03-06 15:01 ` David Ahern
2015-03-06 18:11 ` Mike Galbraith
2015-03-06 18:37 ` David Ahern
2015-03-06 19:29 ` Mike Galbraith
2015-03-10 3:06 ` David Ahern
2015-03-07 9:36 ` Peter Zijlstra
2015-03-06 8:51 ` Peter Zijlstra
2015-03-06 15:03 ` David Ahern
2015-03-06 9:07 ` Peter Zijlstra
2015-03-06 15:10 ` David Ahern [this message]
2015-03-06 9:12 ` Peter Zijlstra
2015-03-06 15:12 ` David Ahern
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=54F9C381.3000305@oracle.com \
--to=david.ahern@oracle.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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
Powered by JetHome