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: Mon, 02 Jul 2012 18:04:58 -0700 (PDT) From: David Miller <davem@...emloft.net> To: bhutchings@...arflare.com Cc: ogerlitz@...lanox.com, roland@...nel.org, yevgenyp@...lanox.com, oren@...lanox.com, netdev@...r.kernel.org, hadarh@...lanox.co.il Subject: Re: [PATCH net-next 06/10] {NET,IB}/mlx4: Add device managed flow steering firmware API Just in case you guys _really_ and _truly_ are so unable to think outside the box that you can't come up with something reasonable, I'll get you started with two ideas: 1) A special "chipset" dummy netdev that a special class of ethtool commands can run on to set these things. 2) A "chipset" genetlink family with suitable operations and attributes. In both cases appropriate mechanisms are added to make for keys that are used for chipset matching, and device drivers simply register a notifier handler that is called on two occaisions: 1) When settings are changed. 2) Upon initial handler registry, to acquire the initial settings. -- 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