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: <20100906174245.GA12956@sgi.com>
Date:	Mon, 6 Sep 2010 10:42:45 -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 Fri, Sep 03, 2010 at 07:30:46PM -0700, David Miller wrote:
> ...
> Likely there would be a set of policies just like the cpu
> power management layer we have.  And there would be a default,
> and userland could override the default.

Thanks. I had thought this over again, and come up with 
something like what you describe. Testing now, and plan 
to send a work-in-progress patch later today for comments.

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

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