[dpdk-dev] [Bug 289] mlx5: 100G interface capability not recognized

[dpdk-dev] [Bug 289] mlx5: 100G interface capability not recognized

[bugzilla]

https://bugs.dpdk.org/show_bug.cgi?id=289

            Bug ID: 289
           Summary: mlx5: 100G interface capability not recognized
           Product: DPDK
           Version: 17.11
          Hardware: All
                OS: All
            Status: CONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: srinivas.narayan@att.com
  Target Milestone: ---

mlx5_link_update uses the newer ethtool command ETHTOOL_GLINKSETTINGS to
determine interface capabilities but falls back to the older (deprecated)
ETHTOOL_GSET command if the new method fails for any reason. The older method
only supports reporting of capabilities up to 40G.

However, mlx5_link_update_unlocked_gs can return a failure for a number of
reasons (including the link being down). Using the older method in cases of
transient failure of the method can result in reporting of reduced capabilities
to the application.

The older method (mlx5_link_update_unlocked_gset) should only be invoked if the
newer method returns EOPNOTSUPP.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[dpdk-dev] [Bug 289] mlx5: 100G interface capability not recognized

[bugzilla]

https://bugs.dpdk.org/show_bug.cgi?id=289

Thomas Monjalon (thomas@monjalon.net) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |thomas@monjalon.net
         Resolution|---                         |FIXED
             Status|CONFIRMED                   |RESOLVED

--- Comment #1 from Thomas Monjalon (thomas@monjalon.net) ---
Fixed in 19.08:
http://git.dpdk.org/dpdk/commit/?id=cb1d2cce95

-- 
You are receiving this mail because:
You are the assignee for the bug.