linux-kernel - Re: 2.6.27/2.6.28: irqbalance dies shortly after starting the daemon on x86 but not x86

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090103010858.GD5181@bombadil.infradead.org>
Date:	Fri, 2 Jan 2009 20:08:58 -0500
From:	Kyle McMartin <kyle@...radead.org>
To:	Justin Piszcz <jpiszcz@...idpixels.com>
Cc:	Arjan van de Ven <arjan@...ux.intel.com>,
	linux-kernel@...r.kernel.org, Kyle McMartin <kyle@...radead.org>
Subject: Re: 2.6.27/2.6.28: irqbalance dies shortly after starting the
	daemon on x86 but not x86_64, why?

On Fri, Jan 02, 2009 at 07:32:21PM -0500, Justin Piszcz wrote:
> The CPU = E6700 so yep, so if there is one physical socket with 4 cores it
> keeps?  For it to keep and not oneshot you need > 2 cores?
>

It depends... if your 4-core is laid out with four cores sharing one
external cache, then it will terminate, if, say you had 4 cores with
each pair sharing a cache (so two external caches) then it would
continue as a daemon. (If you had 2 sockets with a processor in each
one, it would continue running as well no matter how many cores on
each.)

If you run irqbalance --debug, it will show you the topology it detects.
If you have multiple cache domains, and it is still exiting, then we
have a bug. :)

cheers, Kyle
--
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/