All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hangbin Liu <liuhangbin@gmail.com>
To: Nikolay Aleksandrov <razor@blackwall.org>
Cc: Jay Vosburgh <j.vosburgh@gmail.com>,
	netdev@vger.kernel.org, Jiri Pirko <jiri@resnulli.us>
Subject: Re: [Bonding] Should we support qemu/virtio for 802.3ad mode?
Date: Tue, 2 Jul 2024 08:17:37 +0800	[thread overview]
Message-ID: <ZoNHISwvQ_0QeIRp@Laptop-X1> (raw)
In-Reply-To: <ffa1036b-fee0-4e0a-bb5a-791ff95c7142@blackwall.org>

HI Nikolay,

Thanks for your info. I will ask if the customer is OK to set the speed manually.

Regards
Hangbin

On Mon, Jul 01, 2024 at 01:27:54PM +0300, Nikolay Aleksandrov wrote:
> On 01/07/2024 13:11, Hangbin Liu wrote:
> > Hi Jay,
> > 
> > Some one propose again[1] if we should support 802.3ad mode for virtio driver.
> > What do you think? Should we treat the SPEED_UNKNOWN as 1 or something else
> > in __get_link_speed()?
> > 
> > [1] https://lore.kernel.org/all/CAJO99TmB3957Wq3Cse7azgBxKeZ2BV6QihoyAsjUjyvzc-V8dQ@mail.gmail.com/
> > 
> > Thanks
> > Hangbin
> 
> Hi Hangbin,
> Because of 802.3ad we added:
>  commit 16032be56c1f
>  Author: Nikolay Aleksandrov <razor@blackwall.org>
>  Date:   Wed Feb 3 04:04:37 2016 +0100
> 
>     virtio_net: add ethtool support for set and get of settings
>     
>     This patch allows the user to set and retrieve speed and duplex of the
>     virtio_net device via ethtool. Having this functionality is very helpful
>     for simulating different environments and also enables the virtio_net
>     device to participate in operations where proper speed and duplex are
>     required (e.g. currently bonding lacp mode requires full duplex). Custom
>     speed and duplex are not allowed, the user-supplied settings are validated
>     before applying.
>     
>     Example:
>     $ ethtool eth1
>     Settings for eth1:
>     ...
>             Speed: Unknown!
>             Duplex: Unknown! (255)
>     $ ethtool -s eth1 speed 1000 duplex full
>     $ ethtool eth1
>     Settings for eth1:
>     ...
>             Speed: 1000Mb/s
>             Duplex: Full
>     
>     Based on a patch by Roopa Prabhu.
>     
>     Signed-off-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
> 
> You can set any link parameters and use virtio_net with bond/lacp today.
> 
> Cheers,
>  Nik

      reply	other threads:[~2024-07-02  0:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-01 10:11 [Bonding] Should we support qemu/virtio for 802.3ad mode? Hangbin Liu
2024-07-01 10:27 ` Nikolay Aleksandrov
2024-07-02  0:17   ` Hangbin Liu [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=ZoNHISwvQ_0QeIRp@Laptop-X1 \
    --to=liuhangbin@gmail.com \
    --cc=j.vosburgh@gmail.com \
    --cc=jiri@resnulli.us \
    --cc=netdev@vger.kernel.org \
    --cc=razor@blackwall.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.