linux-kernel - Re: NMI watchdog triggering during load

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <54FE5FBD.3060801@oracle.com>
Date:	Mon, 09 Mar 2015 21:06:37 -0600
From:	David Ahern <david.ahern@...cle.com>
To:	Mike Galbraith <efault@....de>
CC:	Peter Zijlstra <peterz@...radead.org>,
	Ingo Molnar <mingo@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: NMI watchdog triggering during load_balance

On 3/6/15 12:29 PM, Mike Galbraith wrote:
> On Fri, 2015-03-06 at 11:37 -0700, David Ahern wrote:
>
>> But, I do not understand how the wrong topology is causing the NMI
>> watchdog to trigger. In the end there are still N domains, M groups per
>> domain and P cpus per group. Doesn't the balancing walk over all of them
>> irrespective of physical topology?
>
> You have this size extra large CPU domain that you shouldn't have,
> massive collisions therein ensue.
>

I was able to get the socket/cores/threads issue resolved, so the 
topology is correct. But still need to check out a few things. Thanks 
Mike and Peter for the suggestions.

David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/