summaryrefslogtreecommitdiff
path: root/include/linux/mlx5
diff options
context:
space:
mode:
authorHuy Nguyen <huyn@mellanox.com>2016-11-27 18:02:05 +0300
committerDavid S. Miller <davem@davemloft.net>2016-11-28 23:09:34 +0300
commit820c2c5e773d283ab102f1b64618e2ddfbb975ef (patch)
tree23409904845c12d1b38960a788cd40cb8c720572 /include/linux/mlx5
parent3a6a931dfb8e49a7377825b465d84e110fe89f68 (diff)
downloadlinux-820c2c5e773d283ab102f1b64618e2ddfbb975ef.tar.xz
net/mlx5e: Read ETS settings directly from firmware
Issue description: Current implementation saves the ETS settings from user in a temporal soft copy and returns this settings when user queries the ETS settings. With the new DCBX firmware, the ETS settings can be changed by firmware when the DCBX is in firmware controlled mode. Therefore, user will obtain wrong values from the temporal soft copy. Solution: 1. Read the ETS settings directly from firmware. 2. For tc_tsa: a. Initialize tc_tsa to vendor IEEE_8021QAZ_TSA_VENDOR at netdev creation. b. When reading ETS setting from FW, if the traffic class bandwidth is less than 100, set tc_tsa to IEEE_8021QAZ_TSA_ETS. This implementation solves the scenarios when the DCBX is in FW control and willing bit is on which means the ETS setting is dictated by remote switch. Also check ETS capability where needed. Signed-off-by: Huy Nguyen <huyn@mellanox.com> Signed-off-by: Saeed Mahameed <saeedm@mellanox.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include/linux/mlx5')
0 files changed, 0 insertions, 0 deletions