d55f3d9c1a
Scheduling rate of port-level in hns3 PF driver configured to
hardware is obtained from firmware, which determines the
bandwidth capability of the port. The rate in firmware is
generally configured with the maximum value for network engine
supporting multiple rates, such as 10G and 25G. It may cause
the following issues:
1) When a 10G optical module is used on the network engine, scheduling
rate of this port will also be configured to hardware with 25G.
However, the MAC rate of this port is 10G. In this case, it is
unreasonable that the port scheduling rate is different from the MAC
rate.
2) If default speed in firmware is not the maximum value, the 25G port
may not reach the capability of the port.
Therefore, we fix configurations of port-level scheduling rate
according to updating of MAC link speed.
Fixes:
|
||
---|---|---|
.. | ||
hns3_cmd.c | ||
hns3_cmd.h | ||
hns3_dcb.c | ||
hns3_dcb.h | ||
hns3_ethdev_vf.c | ||
hns3_ethdev.c | ||
hns3_ethdev.h | ||
hns3_fdir.c | ||
hns3_fdir.h | ||
hns3_flow.c | ||
hns3_intr.c | ||
hns3_intr.h | ||
hns3_logs.h | ||
hns3_mbx.c | ||
hns3_mbx.h | ||
hns3_mp.c | ||
hns3_mp.h | ||
hns3_regs.c | ||
hns3_regs.h | ||
hns3_rss.c | ||
hns3_rss.h | ||
hns3_rxtx_vec_neon.h | ||
hns3_rxtx_vec_sve.c | ||
hns3_rxtx_vec.c | ||
hns3_rxtx_vec.h | ||
hns3_rxtx.c | ||
hns3_rxtx.h | ||
hns3_stats.c | ||
hns3_stats.h | ||
meson.build | ||
version.map |