summaryrefslogtreecommitdiffstats
path: root/tools
diff options
context:
space:
mode:
authoryongari <yongari@FreeBSD.org>2013-06-10 07:31:49 +0000
committeryongari <yongari@FreeBSD.org>2013-06-10 07:31:49 +0000
commit015913b3831336ed004e485e122a772a0d8c5a67 (patch)
tree3c818dab5ef36eed9bc2f4ac7d6ce78155cf35dc /tools
parent4e8602cd3988d7feb832032e4eb9c5a560af08f0 (diff)
downloadFreeBSD-src-015913b3831336ed004e485e122a772a0d8c5a67.zip
FreeBSD-src-015913b3831336ed004e485e122a772a0d8c5a67.tar.gz
Avoid unnecessary controller reinitialization by checking driver
running state. fxp(4) requires controller reinitialization for the following cases. o RX lockup condition on i82557 o promiscuous mode change o multicast filter change o WOL configuration o TSO/VLAN hardware tagging/checksum offloading configuration o MAC reprogramming after speed/duplex/flow-control resolution o Any events that result in MAC reprogramming(link UP/DOWN, remote link partner's restart of auto-negotiation etc) o Microcode loading/unloading Apart from above cases which come from hardware limitation, upper stack also blindly reinitializes controller whenever an IP address is assigned. After r194573, fxp(4) no longer needs to reinitialize the controller to program multicast filter after upping the interface. So keeping track of driver running state should remove all unnecessary controller reinitializations. This change will also address endless controller reinitialization triggered by dhclient(8). Tested by: hrs, Alban Hertroys <haramrae@gmail.com>
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud