[PATCH] hang on ZEROCOPY/TSO when hitting no-Tx-resources
* Critical bug fix: under heavy Tx stress using ZEROCOPY or TSO, if we ran out of Tx descriptors, we didn't calculate for the context descritor used as the first of the ZEROCOPY/TSO send, nor do we clean up the context desriptor bits in the case where the send isn't going to fit, where we need to undo the mappings. This bug was introduced with the 5.2.16 patch set which included a workaround for a hang on 82544 over PCI-X. This workaround cause the check for no-Tx- rosource logic to change, and this bug slipped in.
Showing
Please register or sign in to comment