e847c7675e
If the number of lanes was forced and then subsequently the user
omits this parameter, the ksettings->lanes is reset. The driver
should then reset the number of lanes to the device's default
for the specified speed.
However, although the ksettings->lanes is set to 0, the mod variable
is not set to true to indicate the driver and userspace should be
notified of the changes.
The consequence is that the same ethtool operation will produce
different results based on the initial state.
If the initial state is:
$ ethtool swp1 | grep -A 3 'Speed: '
Speed: 500000Mb/s
Lanes: 2
Duplex: Full
Auto-negotiation: on
then executing 'ethtool -s swp1 speed 50000 autoneg off' will yield:
$ ethtool swp1 | grep -A 3 'Speed: '
Speed: 500000Mb/s
Lanes: 2
Duplex: Full
Auto-negotiation: off
While if the initial state is:
$ ethtool swp1 | grep -A 3 'Speed: '
Speed: 500000Mb/s
Lanes: 1
Duplex: Full
Auto-negotiation: off
executing the same 'ethtool -s swp1 speed 50000 autoneg off' results in:
$ ethtool swp1 | grep -A 3 'Speed: '
Speed: 500000Mb/s
Lanes: 1
Duplex: Full
Auto-negotiation: off
This patch fixes this behavior. Omitting lanes will always results in
the driver choosing the default lane width for the chosen speed. In this
scenario, regardless of the initial state, the end state will be, e.g.,
$ ethtool swp1 | grep -A 3 'Speed: '
Speed: 500000Mb/s
Lanes: 2
Duplex: Full
Auto-negotiation: off
Fixes:
|
||
---|---|---|
.. | ||
bitset.c | ||
bitset.h | ||
cabletest.c | ||
channels.c | ||
coalesce.c | ||
common.c | ||
common.h | ||
debug.c | ||
eee.c | ||
eeprom.c | ||
features.c | ||
fec.c | ||
ioctl.c | ||
linkinfo.c | ||
linkmodes.c | ||
linkstate.c | ||
Makefile | ||
mm.c | ||
module.c | ||
netlink.c | ||
netlink.h | ||
pause.c | ||
phc_vclocks.c | ||
plca.c | ||
privflags.c | ||
pse-pd.c | ||
rings.c | ||
rss.c | ||
stats.c | ||
strset.c | ||
tsinfo.c | ||
tunnels.c | ||
wol.c |