From: Jacob Keller <jacob.e.keller@intel.com>
To: Jamie Gloudon <jamie.gloudon@gmx.fr>, netdev@vger.kernel.org
Subject: Re: Broken link partner advertised reporting in ethtool
Date: Mon, 27 Jul 2020 12:19:13 -0700 [thread overview]
Message-ID: <871802ee-3b9a-87fb-4a16-db570828ef2d@intel.com> (raw)
In-Reply-To: <20200727154715.GA1901@gmx.fr>
On 7/27/2020 8:47 AM, Jamie Gloudon wrote:
> Hey,
>
> While having a discussion with Sasha from Intel. I noticed link partner
> advertised support is broken in ethtool 5.7. Sasha hinted to me, the
> new API that ethtool is using.
>
> I see the actual cause in dump_peer_modes() in netlink/settings.c, that
> the mask parameter is set to false for dump_link_modes, dump_pause and
> bitset_get_bit.
>
> Regards,
> Jamie Gloudon
>
Hi,
Seems like more detail here would be useful. This is about the ethtool
application.
Answering the following questions would help:
- what you wanted to achieve;
- what you did (including what versions of software and the command
sequence to reproduce the behavior);
- what you saw happen;
- what you expected to see; and
- how the last two are different.
The mask parameter for dump_link_modes is used to select between
displaying the mask and the value for a bitset.
According to the source in filling the LINKMODES_PEER, we actually don't
send a mask at all with this setting, so using true for the mask in
dump_link_modes here seems like it would be wrong.
It appears that to get link partner settings your driver must fill in
lp_advertising. If you're referring to an Intel driver, a quick search
over drivers/net/ethernet/intel shows that only the ice driver currently
supports reporting this information.
Given this, I am not convinced there is a bug in ethtool.
Thanks,
Jake
next prev parent reply other threads:[~2020-07-27 19:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 15:47 Broken link partner advertised reporting in ethtool Jamie Gloudon
2020-07-27 19:19 ` Jacob Keller [this message]
2020-07-27 20:09 ` Jamie Gloudon
2020-07-27 20:42 ` Michal Kubecek
2020-07-27 21:01 ` Andrew Lunn
2020-07-27 21:08 ` Michal Kubecek
2020-07-27 21:25 ` Andrew Lunn
2020-07-27 21:30 ` Jacob Keller
2020-07-27 21:42 ` Jacob Keller
2020-07-27 21:27 ` Jacob Keller
2020-07-27 22:00 ` Michal Kubecek
2020-07-27 22:15 ` Jacob Keller
2020-07-27 21:18 ` Jacob Keller
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=871802ee-3b9a-87fb-4a16-db570828ef2d@intel.com \
--to=jacob.e.keller@intel.com \
--cc=jamie.gloudon@gmx.fr \
--cc=netdev@vger.kernel.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).