When the host boots, it hints set the epair queue max len to 86016. I did not see any related problem When I set it, it's stable. But epair consumed cpu, it's so easy to touch 100% cpu usage if it's passed high rate packets.
Simon 20180703 On 2018/7/3 06:16, Bjoern A. Zeeb wrote: > On 2 Jul 2018, at 21:11, Dr Josef Karthauser wrote: > >> We’re experiencing a strange issue in production failure with epair >> (which we’re using to talk vimage to jails). >> >> FreeBSD s5 11.1-STABLE FreeBSD 11.1-STABLE #2 r328930: Tue Feb 6 >> 16:05:59 GMT 2018 root@s5:/usr/obj/usr/src/sys/TRUESPEED amd64 >> >> Looks like epair has suddenly stopped forwarding packets between the >> pair interfaces. Our server has been up for 82 days and it’s been >> working fine, but suddenly packets have stopped being forwarded >> between epairs across the entire system. (We’ve got around 30 epairs >> on the host). So, we’ve got a sudden ARP resolution failure which is >> affecting all services. :(. > > Ok, that’s a very interesting new observation I have not heard before or > missed. You are saying that for about 30 epair pairs NONE is working > anymore? All 30 are “dead”? > > /bz > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" _______________________________________________ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
