| commit | d02615d118d1bd6c4ae3ecae5405687688d28b60 | |
| author | Sepherosa Ziehau <sephe@dragonflybsd.org> | |
| Sun, 21 Jan 2007 10:44:45 +0000 (21 10:44 +0000) | ||
| committer | Sepherosa Ziehau <sephe@dragonflybsd.org> | |
| Sun, 21 Jan 2007 10:44:45 +0000 (21 10:44 +0000) | ||
| tree | 5fff25782979a9e57cb4b5f91b7f7c88031e9b9c | treesnapshot (tar.gz zip) |
| parent | efcddd2205b33f8b4e5591ea745c3c3c320cf100 | commitdiff |
Add a workaround for some Lenovo/IBM laptops' onboard em(4).
Without this workaround, em(4) is extremely slow when TXing packets, though
polling(4) seems to make the situation better, the speed is still far from
expectation for 100BaseTX-FDX network.
Reported-by: Michal Belczyk <belczyk@bsd.krakow.pl>
Obtained-from: FreeBSD-current mail list, Jack Vogel <jfvogel@gmail.com>
# According to Jack Vogel:
# "saying its known to be a problem doesnt mean its cause is known"
Without this workaround, em(4) is extremely slow when TXing packets, though
polling(4) seems to make the situation better, the speed is still far from
expectation for 100BaseTX-FDX network.
Reported-by: Michal Belczyk <belczyk@bsd.krakow.pl>
Obtained-from: FreeBSD-current mail list, Jack Vogel <jfvogel@gmail.com>
# According to Jack Vogel:
# "saying its known to be a problem doesnt mean its cause is known"
| sys/dev/netif/em/if_em.c | diffblobblamehistory |