From: David Ahern <david.ahern@oracle.com>
To: Mike Galbraith <efault@gmx.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
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:01:41 -0700 [thread overview]
Message-ID: <54F9C155.3050309@oracle.com> (raw)
In-Reply-To: <1425617559.16821.36.camel@gmx.de>
On 3/5/15 9:52 PM, Mike Galbraith wrote:
>> CPU970 attaching sched-domain:
>> domain 0: span 968-975 level SIBLING
>> groups: 8 single CPU groups
>> domain 1: span 968-975 level MC
>> groups: 1 group with 8 cpus
>> domain 2: span 768-1023 level CPU
>> groups: 4 groups with 256 cpus per group
>
> Wow, that topology is horrid. I'm not surprised that your box is
> writhing in agony. Can you twiddle that?
>
twiddle that how?
The system has 4 physical cpus (sockets). Each cpu has 32 cores with 8
threads per core and each cpu has 4 memory controllers.
If I disable SCHED_MC and CGROUPS_SCHED (group scheduling) there is a
noticeable improvement -- watchdog does not trigger and I do not get the
rq locks held for 2-3 seconds. But there is still fairly high cpu usage
for an idle system. Perhaps I should leave SCHED_MC on and disable
SCHED_SMT; I'll try that today.
Thanks,
David
next prev parent reply other threads:[~2015-03-06 15:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 4:05 NMI watchdog triggering during load_balance David Ahern
2015-03-06 4:52 ` Mike Galbraith
2015-03-06 15:01 ` David Ahern [this message]
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
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=54F9C155.3050309@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;
as well as URLs for NNTP newsgroup(s).