linux-kernel - Re: [RFC/PATCH] notify user-level IRQ balancer when kernel assigns IRQ affinity

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]

Date:	Fri, 03 Sep 2010 14:48:33 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	akepner@....com
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [RFC/PATCH] notify user-level IRQ balancer when kernel assigns
 IRQ affinity

From: Arthur Kepner <akepner@....com>
Date: Fri, 3 Sep 2010 14:05:54 -0700

> 
> We've run into situations where a CPU runs out of interrupt 
> vectors, because all the interrupts are getting the default 
> affinity (and the interrupt balancer hasn't yet run).
> 
> The following emits a netlink message whenever an interrupt 
> is given a default CPU affinity. A user-level IRQ balancer 
> can use those messages to decide if, and how to reassign 
> affinities. This should allow us to avoid running out of 
> vectors on any particular CPU (or at least make it far less 
> likely).
> 
> I know this needs work, but would like to get comments on 
> the idea before doing more coding and testing.
> 
> Signed-off-by: Arthur Kepner <akepner@....com>

As I replied to you on netdev, this can't possibly work.

Interrupt allocation needs to work properly before userspace
even starts up.  So the allocation management must be inside
of the kernel entirely.

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