Support out-of-order TX completion notifications

Apparently, just like the disk interface, the network backend may
post TX completions out-of-order, i.e. the ring position doesn't
determine which descriptor is being completed and the code must
look at the response id inside the completion message.  It might
seem obvious, but since networking hardware doesn't usually work
this way, it was something that has been overlooked.

Based on instability reports from Kirill Miazine <km at krot ! org>,
thanks!

0 files changed, 0 insertions, 0 deletions