summaryrefslogtreecommitdiff
path: root/net/rfkill
diff options
context:
space:
mode:
authorGovindarajulu Varadarajan <_govind@gmx.com>2015-08-16 01:44:54 +0530
committerDavid S. Miller <davem@davemloft.net>2015-08-17 15:25:29 -0700
commit373fb0873d4325a7afa04aec29ced0c122d1f8a9 (patch)
treeb0da4fd30b4dde4e505b3e84339d24a0a85d683f /net/rfkill
parentfda3f52bdbbe576d78ca9ea84912b48fa51f0e90 (diff)
enic: add devcmd2
devcmd is an interface for driver to communicate with fw/adaptor. It involves writing data to hardware registers and waiting for the result. This mechanism does not scale well. The queuing of "no wait" devcmds is done in firmware memory rather than on the host. Firmware memory is a rather more scarce and valuable resource than host memory. A devcmd storm from one vf can disrupt the service on other pf/vf. The lack of flow control allows for possible denial of server from one VM to another. Devcmd2 uses work queue to post the devcmds, just like tx work queue. This allows better flow control. Initialize devcmd2, if fails we fall back to devcmd1. Also change the driver version. Signed-off-by: N V V Satyanarayana Reddy <nalreddy@cisco.com> Signed-off-by: Govindarajulu Varadarajan <_govind@gmx.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/rfkill')
0 files changed, 0 insertions, 0 deletions