linux-kernel - Re: IRQ affinities

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: <48344B3D.5010404@qualcomm.com>
Date:	Wed, 21 May 2008 09:18:05 -0700
From:	Max Krasnyanskiy <maxk@...lcomm.com>
To:	Arjan van de Ven <arjan@...radead.org>
CC:	Paul Jackson <pj@....com>, Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	menage@...gle.com, mingo@...e.hu, linux-kernel@...r.kernel.org
Subject: Re: IRQ affinities

Arjan van de Ven wrote:
> On Tue, 20 May 2008 18:14:58 -0700
> Max Krasnyanskiy <maxk@...lcomm.co
> 
>> For the IRQs specifically all I need is to be able to tell the kernel
>> to not route IRQs to certain CPUs. That's mostly works already via 
>> /proc/irq/N/smp_affinity, the problem is dynamically allocated irqs
>> because /proc/irq/N directory does not exist until those IRQs are
>> allocated/enabled.
> \\
> 
> why don't you tell irqbalance instead? it'll make sure the irq stays
> out of the wind...
> 

That will be too late. By the time irqbalance sees that IRQ it may have 
already fired (possibly several times) on the "wrong" processor.

Max

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