I am working on enabling Linux Bonding feature where the Copper (IGB) and Fibre (ICE) ports are slaves of a bond interface.
I would like to understand whether both these drivers support bonding and to what extent.
Specifically, do these drivers support APIs like netif_carrier_ok().
https://www.kernel.org/doc/Documentation/networking/bonding.txt
use_carrier
Specifies whether or not miimon should use MII or ETHTOOL
ioctls vs. netif_carrier_ok() to determine the link
status. The MII or ETHTOOL ioctls are less efficient and
utilize a deprecated calling sequence within the kernel. The
netif_carrier_ok() relies on the device driver to maintain its
state with netif_carrier_on/off; at this writing, most, but
not all, device drivers support this facility.
We have stringent requirements to do a faster switchover from active to backup slave link during link failover.
That needs the drivers to respond faster to link status change and a subsequent faster response to switch role to active and start forwarding packets.
More details can be found here:
https://docs.kernel.org/networking/operstates.html
Appreciate any leads in this regard.
Here are the versions in use in the box:
[0:/]$ ethtool -i ha_portC
driver: igb
version: 5.0.3-k
firmware-version: 1.96, 0x80000f88
expansion-rom-version:
bus-info: 0000:18:00.1
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no
[0:/]$ ethtool -i ha_portF
driver: ice
version: 1.11.14
firmware-version: 2.28 0x8001028f 1.3200.0
expansion-rom-version:
bus-info: 0000:89:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes
