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: <alpine.DEB.1.10.0901021931140.19502@p34.internal.lan>
Date:	Fri, 2 Jan 2009 19:32:21 -0500 (EST)
From:	Justin Piszcz <jpiszcz@...idpixels.com>
To:	Arjan van de Ven <arjan@...ux.intel.com>
cc:	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, 2 Jan 2009, Arjan van de Ven wrote:

> Justin Piszcz wrote:
>> (same on both x86 and x86_64):
>> # cat /etc/default/irqbalance
>> #Configuration for the irqbalance daemon
>> 
>> #Should irqbalance be enabled?
>> ENABLED=1
>> #Balance the IRQs only once?
>> ONESHOT="0"
>
>
> which version of irqbalance is this?
>

$ dpkg -l | grep -i irqbalance
ii  irqbalance                           0.55-2.4                      Daemon to balance interrupts for SMP systems

Kyle stated:
> If there is only one cache domain, ie: one physical cpu socket with two
> cores sharing a cache, then irqbalance will return after the initial
> balance since it would be pointless to continue running. (It forces
> itself into oneshot mode.)

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?

Justin.

--
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/