diff options
author | David S. Miller <davem@davemloft.net> | 2018-03-22 20:29:05 +0100 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2018-03-22 20:29:05 +0100 |
commit | 6686c459e1449a3ee5f3fd313b0a559ace7a700e (patch) | |
tree | d8e84a2ba3f2621b5d67a1d96d6c3a2637ca3d44 /net/l2tp | |
parent | Merge branch 'Rework-ip_ra_chain-protection' (diff) | |
parent | net: hns3: Changes required in PF mailbox to support VF reset (diff) | |
download | linux-6686c459e1449a3ee5f3fd313b0a559ace7a700e.tar.xz linux-6686c459e1449a3ee5f3fd313b0a559ace7a700e.zip |
Merge branch 'hns3-VF-reset'
Salil Mehta says:
====================
Add support of VF Reset to HNS3 VF driver
This patch-set adds the support of VF reset to the existing VF driver.
VF Reset can be triggered due to TX watchdog firing as a result of TX
data-path not working. VF reset could also be a result of some internal
configuration changes if that requires reset, or as a result of the
PF/Core/Global/IMP(Integrated Management Processor) reset happened in
the PF.
Summary of Patches:
* Watchdog timer trigger chnages are present in Patch 1.
* Reset Service Task and related Event handling is present in Patches {2,3}
* Changes to send reset request to PF, reset stack and re-initialization
of the hclge device is present in Patches {4,5,6}
* Changes related to ARQ (Asynchronous Receive Queue) and its event handling
are present in Patches {7,8}
* Changes required in PF to handle the VF Reset request and actually perform
hardware VF reset is there in Patch 9.
NOTE: This patch depends upon "[PATCH net-next 00/11] fix some bugs for HNS3 driver"
Link: https://lkml.org/lkml/2018/3/21/72
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/l2tp')
0 files changed, 0 insertions, 0 deletions