On 20 January 2016 at 00:46, Jonathon Sisson <open...@j3z.org> wrote: > On Tue, Jan 19, 2016 at 06:17:40PM +0100, Mike Belopuhov wrote: >> On 19 January 2016 at 17:02, Mike Belopuhov <m...@belopuhov.com> wrote: >> > That's OK. Thank you for taking your time to test it. >> > I can reproduce the problem with tcpbench as well and >> > hopefully will have a solution soon. >> >> OK, this should be fixed in current. Please update and test :-) >> > Mike, > > I appreciate the update. I've rebuilt with CURRENT code checked out > as of a few hours ago and now I'm 99% certain I can't reproduce =) >
Great! > To test, I pushed 4 simultaneous uploads and the instance remained > responsive. Afterwards, I noted this: > > # netstat -sI xnf0 > Name Mtu Network Address Ipkts Ierrs Opkts Oerrs > Colls > xnf0 1500 <Link> 12:dd:e7:6d:a9:49 1901330 0 4210541 48602 > 0 > xnf0 1500 172.31.47/2 ip-172-31-47-76.e 1901330 0 4210541 48602 > 0 > > I don't know if the output errors are an issue, but I thought I'd > mention it regardless. > Indeed. I was accounting for tx ring full events as output errors during debugging. Now it's time to move on. That said, it should be fixed by my last commit. Thanks for reporting! > I really appreciate your quick answers and fix. Thank you, and the > rest of the team, for OpenBSD. > > -Jonathon
