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] [day] [month] [year] [list]

Message-Id: <20100906.125123.104055684.davem@davemloft.net>
Date:	Mon, 06 Sep 2010 12:51:23 -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: Mon, 6 Sep 2010 10:42:45 -0700

> On Fri, Sep 03, 2010 at 07:30:46PM -0700, David Miller wrote:
>> This also means there would have to be notifications sent to
>> drivers when the distribution and allocation policy of MSI-X
>> interrupts is changed.  This is so that, for example, network
>> drivers can reconfigure their network queues for the new set
>> of MSI-X vectors available to them after the policy change.
> 
> Hadn't considered this. Will have to add it.

BTW, reading this again made me consider another case that
needs to invoke a notifier.

Let's say that a policy specifies an even distribution of
MSI-X allocation amongst all present devices behind a PCI
domain.  Well, if a PCI-E device hot-plugs you'll have to
do notifications for that too because a card might now be
able to get more of the MSI-X vectors it wants.
--
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