> > If that made difference, all other ethernet controllers would have > suffered from the similar issues. > Well, some commit done between June 7 and June 15 made a difference, but I have no idea what or why.
Also, I had a report of very poor read rate from someone using a bge(4) interface, but I have no reason to believe it is because of the same issue. > > If you have some spare time please try attach one. I guess fast > ethernet controller has smaller FIFO size than that of GigE > controller so it is frequently triggered the issue on fast ethernet > controller than GigE controllers. I still guess that there are > cases that an interrupt is not correctly served such that driver > missed a lot of frames. > Patch didn't help. If anything it degrading things a bit (stats are attached). rick
re0 statistics: Tx frames : 102009 Rx frames : 133318 Tx errors : 0 Rx errors : 0 Rx missed frames : 15246 Rx frame alignment errs : 0 Tx single collisions : 0 Tx multiple collisions : 0 Rx unicast frames : 133306 Rx broadcast frames : 0 Rx multicast frames : 12 Tx aborts : 0 Tx underruns : 0
_______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
