summaryrefslogtreecommitdiffstats
path: root/net/bluetooth/hci_request.c
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2015-08-17 15:25:30 -0700
committerDavid S. Miller <davem@davemloft.net>2015-08-17 15:25:30 -0700
commit863960b4c5c564819b153d53cffdf3f68283eaa2 (patch)
treeb0da4fd30b4dde4e505b3e84339d24a0a85d683f /net/bluetooth/hci_request.c
parent2ea273d76a4869c097c6b1a1070162add2f66a6e (diff)
parent373fb0873d4325a7afa04aec29ced0c122d1f8a9 (diff)
downloadop-kernel-dev-863960b4c5c564819b153d53cffdf3f68283eaa2.zip
op-kernel-dev-863960b4c5c564819b153d53cffdf3f68283eaa2.tar.gz
Merge branch 'enic-devcmd2'
Govindarajulu Varadarajan says: ==================== enic: add devcmd2 This series adds new devcmd2 support. The first two patches are code refactoring. 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. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/bluetooth/hci_request.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud