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]

Message-Id: <20100826.122407.260097270.davem@davemloft.net>
Date:	Thu, 26 Aug 2010 12:24:07 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	akepner@....com
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH] mlx4_core: module param to limit msix vec allocation

From: Arthur Kepner <akepner@....com>
Date: Thu, 26 Aug 2010 10:06:46 -0700

> Use a module parameter to limit the number of MSI-X vectors that 
> the mlx4_core driver will attempt to allocate.
> 
> Signed-off-by: Arthur Kepner <akepner@....com>

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.

I am not applying this patch, sorry.
--
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