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
| ||
|
Date: Fri, 03 Sep 2010 19:30:46 -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: Fri, 3 Sep 2010 15:13:03 -0700 > On Fri, Sep 03, 2010 at 02:46:58PM -0700, David Miller wrote: >> No, you really can't do it this way, IRQ allocation management has to >> be in the kernel. > > Really? I was specifically trying to avoid that, and let the > policy about interrupt assignment be done in a user process. > > Do you have any specific ideas about how that'd look? 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. 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. -- 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
Powered by blists - more mailing lists