netdev - Re: [PATCH] mlx4_core: module param to limit msix vec allocation

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, 3 Sep 2010 13:30:44 -0700
From:	Arthur Kepner <akepner@....com>
To:	David Miller <davem@...emloft.net>
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH] mlx4_core: module param to limit msix vec allocation

On Thu, Aug 26, 2010 at 12:24:07PM -0700, David Miller wrote:
> ....
> And what the heck happens if every single device driver tries to
> handle this problem in the same way?  It makes no sense to make
> the user specify N special module parameters just to get a working
> system using MSI-X.
> 
> This must be fixed in a centralized way that allows coordination
> between devices which compete for MSI-X vector resources, rather than
> in a way that is specific to each and every device type.
> 

OK, how about this. Each time the kernel assigns a default 
affinity for an interrupt, it generates a netlink message, 
and a user-level interrupt balancer can decide whether and 
how to reassign the interrupt? 

I have that running on a (very small) system and it seems to 
work OK. Will send out the patch in just a minute.

-- 
Arthur
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html