linux-kernel - Re: [patch] Add allowed_affinity to the irq_desc to make it possible to have restricted irqs

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: <86802c440612132224w795f3e01qfeee7183b791922c@mail.gmail.com>
Date:	Wed, 13 Dec 2006 22:24:41 -0800
From:	"Yinghai Lu" <yinghai.lu@....com>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	"Arjan van de Ven" <arjan@...ux.intel.com>,
	"Ingo Molnar" <mingo@...e.hu>, linux-kernel@...r.kernel.org
Subject: Re: [patch] Add allowed_affinity to the irq_desc to make it possible to have restricted irqs

On 12/13/06, Eric W. Biederman <ebiederm@...ssion.com> wrote:
> Arjan van de Ven <arjan@...ux.intel.com> writes:
> > the numa case is already handled; the needed info for that is exposed already
> > enough... at least for irqbalance
>
> What is the problem you are trying to solve?
>
> If it is just interrupts irqbalanced can't help with we can do that
> with a single bit.
>
> My basic problem with understanding what this patch is trying to
> solve is that I've seen some theoretical cases raised but I don't see
> the real world problem.

Good question.

irqbalance could use set_affinity from boot cpu to final cpu.

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