From: Thomas Falcon <tlfalcon@linux.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>, netdev@vger.kernel.org
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH net-next] ibmveth: Allow users to update reported speed and duplex
Date: Tue, 6 Aug 2019 09:41:15 -0500 [thread overview]
Message-ID: <071fe53c-0e89-d221-16be-80d916d3e712@linux.ibm.com> (raw)
In-Reply-To: <87zhkmvbec.fsf@concordia.ellerman.id.au>
On 8/6/19 5:25 AM, Michael Ellerman wrote:
> Thomas Falcon <tlfalcon@linux.ibm.com> writes:
>> Reported ethtool link settings for the ibmveth driver are currently
>> hardcoded and no longer reflect the actual capabilities of supported
>> hardware. There is no interface designed for retrieving this information
>> from device firmware nor is there any way to update current settings
>> to reflect observed or expected link speeds.
>>
>> To avoid confusion, initially define speed and duplex as unknown and
> Doesn't that risk break existing setups?
You're right, sorry for missing that.
>
>> allow the user to alter these settings to match the expected
>> capabilities of underlying hardware if needed. This update would allow
>> the use of configurations that rely on certain link speed settings,
>> such as LACP. This patch is based on the implementation in virtio_net.
> Wouldn't it be safer to keep the current values as the default, and then
> also allow them to be overridden by a motivated user.
That is a good compromise. I will resend an updated version soon with
that change.
Thanks!
>
> cheers
>
prev parent reply other threads:[~2019-08-06 14:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 19:24 [PATCH net-next] ibmveth: Allow users to update reported speed and duplex Thomas Falcon
2019-08-06 10:25 ` Michael Ellerman
2019-08-06 14:41 ` Thomas Falcon [this message]
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=071fe53c-0e89-d221-16be-80d916d3e712@linux.ibm.com \
--to=tlfalcon@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--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).