From: Mike Galbraith <efault@gmx.de>
To: David Ahern <david.ahern@oracle.com>
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 19:11:51 +0100 [thread overview]
Message-ID: <1425665511.7562.36.camel@gmx.de> (raw)
In-Reply-To: <54F9C155.3050309@oracle.com>
On Fri, 2015-03-06 at 08:01 -0700, David Ahern wrote:
> 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?
That was the question, _do_ you have any control, because that topology
is toxic. I guess your reply means 'nope'.
> The system has 4 physical cpus (sockets). Each cpu has 32 cores with 8
> threads per core and each cpu has 4 memory controllers.
Thank god I've never met one of these, looks like the box from hell :)
> 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.
Well, if you disable SMT,your troubles _should_ shrink radically, as
your box does. You should probably look at why you have CPU domains.
You don't ever want to see that on a NUMA box.
-Mike
next prev parent reply other threads:[~2015-03-06 18:12 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
2015-03-06 18:11 ` Mike Galbraith [this message]
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=1425665511.7562.36.camel@gmx.de \
--to=efault@gmx.de \
--cc=david.ahern@oracle.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.