[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20171227.164334.2079471466039224265.davem@davemloft.net>
Date: Wed, 27 Dec 2017 16:43:34 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: jbaron@...mai.com
Cc: netdev@...r.kernel.org, virtualization@...ts.linux-foundation.org,
qemu-devel@...gnu.org, mst@...hat.com, jasowang@...hat.com
Subject: Re: [PATCH net-next v2 1/3] virtio_net: propagate linkspeed/duplex
settings from the hypervisor
From: Jason Baron <jbaron@...mai.com>
Date: Fri, 22 Dec 2017 16:54:01 -0500
> The ability to set speed and duplex for virtio_net in useful in various
> scenarios as described here:
>
> 16032be virtio_net: add ethtool support for set and get of settings
>
> However, it would be nice to be able to set this from the hypervisor,
> such that virtio_net doesn't require custom guest ethtool commands.
>
> Introduce a new feature flag, VIRTIO_NET_F_SPEED_DUPLEX, which allows
> the hypervisor to export a linkspeed and duplex setting. The user can
> subsequently overwrite it later if desired via: 'ethtool -s'.
>
> Signed-off-by: Jason Baron <jbaron@...mai.com>
> Cc: "Michael S. Tsirkin" <mst@...hat.com>
> Cc: Jason Wang <jasowang@...hat.com>
Looks mostly fine to me but need some virtio_net reviewers on this one.
> @@ -57,6 +57,8 @@
> * Steering */
> #define VIRTIO_NET_F_CTRL_MAC_ADDR 23 /* Set MAC address */
>
> +#define VIRTIO_NET_F_SPEED_DUPLEX 63 /* Host set linkspeed and duplex */
> +
Why use a value so far away from the largest existing one?
Just curious.
Powered by blists - more mailing lists