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:10:23 -0700
From:	David Daney <ddaney@...iumnetworks.com>
To:	Arthur Kepner <akepner@....com>
CC:	linux-kernel@...r.kernel.org, David Miller <davem@...emloft.net>
Subject: Re: [RFC/PATCH] notify user-level IRQ balancer when kernel assigns
 IRQ	affinity

On 09/03/2010 02:05 PM, Arthur Kepner wrote:
>
> 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>
>
> ---
>
> diff --git a/arch/Kconfig b/arch/Kconfig
> index 4877a8c..65c79c7 100644
> --- a/arch/Kconfig
> +++ b/arch/Kconfig
> @@ -158,4 +158,15 @@ config HAVE_PERF_EVENTS_NMI
>   	  subsystem.  Also has support for calculating CPU cycle events
>   	  to determine how many clock cycles in a given period.
>
> +config NOTIFY_USER_IRQ_BALANCER
> +	bool "Notify user-level IRQ balancer (EXPERIMENTAL)"
> +	default n
> +	depends on NET&&  X86

Missing a space before that '&&', but more importantly, what part of the 
patch is x86 specific?


David Daney


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