From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 289] mlx5: 100G interface capability not recognized
Date: Fri, 31 May 2019 16:10:19 +0000 [thread overview]
Message-ID: <bug-289-3@http.bugs.dpdk.org/> (raw)
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.
next reply other threads:[~2019-05-31 16:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 16:10 bugzilla [this message]
2019-07-11 8:23 ` bugzilla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-289-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).