Thread (45 messages) flat view 45 messages, 7 authors, 2012-07-03

Re: [PATCH net-next 06/10] {NET,IB}/mlx4: Add device managed flow steering firmware API

From: Or Gerlitz <hidden>
Date: 2012-07-03 11:10:37

On 7/3/2012 4:04 AM, David Miller wrote:
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.
Dave,

Thanks for trying to address the need here, as I wrote you, we've 
removed the module param
from the patch-set and will submit V1 without this. Once the comments 
are over and hopefully
the patches are accepted, we'll see what can/need to be done for 
allowing that flexibility.

Or.

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.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help