CVSROOT: /cvs Module name: src Changes by: mi...@cvs.openbsd.org 2017/07/14 12:24:51
Modified files: sys/dev/pv : if_xnf.c Log message: 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!