qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: Jason Baron <jbaron@akamai.com>,
	qemu-devel@nongnu.org, virtio-dev@lists.oasis-open.org
Subject: Re: [Qemu-devel] [PATCH 4/4] virtio-net: add linkspeed and duplex settings to virtio-net
Date: Fri, 2 Mar 2018 22:19:42 +0200	[thread overview]
Message-ID: <20180302221831-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <7fc612d0-9610-9b07-d054-bb1438898f47@redhat.com>

On Fri, Mar 02, 2018 at 03:14:01PM +0800, Jason Wang wrote:
> 
> 
> On 2018年03月02日 11:46, Jason Baron wrote:
> > Although linkspeed and duplex can be set in a linux guest via 'ethtool -s',
> > this requires custom ethtool commands for virtio-net by default.
> > 
> > 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'.
> > 
> > Linkspeed and duplex settings can be set as:
> > '-device virtio-net,speed=10000,duplex=full'
> 
> I was thinking whether or not it's better to decide the duplex by the type
> of backends.
> 
> E.g userspace and vhost-kernel implement a in fact half duplex. But dpdk
> implement a full duplex.
> 
> Thanks

OTOH it's a priority for some people to be able to support migration
between different backend types. Breaking that won't be nice.

> > 
> > where speed is [0...INT_MAX], and duplex is ["half"|"full"].
> > 
> > Signed-off-by: Jason Baron<jbaron@akamai.com>
> > Cc: "Michael S. Tsirkin"<mst@redhat.com>
> > Cc: Jason Wang<jasowang@redhat.com>
> > Cc:virtio-dev@lists.oasis-open.org
> > ---

  parent reply	other threads:[~2018-03-02 20:19 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-02  3:46 [Qemu-devel] [PATCH 0/4] virtio-net: allow linkspeed and duplex setting Jason Baron
2018-03-02  3:46 ` [Qemu-devel] [PATCH 1/4] eth: add speed and duplex definitions Jason Baron
2018-03-02 17:54   ` Michael S. Tsirkin
2018-03-06 17:53     ` Jason Baron
2018-03-06 18:15       ` Michael S. Tsirkin
2018-03-08  3:46         ` Jason Baron
2018-03-02  3:46 ` [Qemu-devel] [PATCH 2/4] rocker: drop local " Jason Baron
2018-03-02 17:57   ` Michael S. Tsirkin
2018-03-02  3:46 ` [Qemu-devel] [PATCH 3/4] virtio-net: use 64-bit values for feature flags Jason Baron
2018-03-02  3:46 ` [Qemu-devel] [PATCH 4/4] virtio-net: add linkspeed and duplex settings to virtio-net Jason Baron
2018-03-02  7:14   ` Jason Wang
2018-03-02 16:59     ` Jason Baron
2018-03-02 20:22       ` Michael S. Tsirkin
2018-03-06 17:57         ` Jason Baron
2018-03-02 20:19     ` Michael S. Tsirkin [this message]
2018-03-04 13:05       ` [Qemu-devel] [virtio-dev] " Yan Vugenfirer
2018-03-06 18:02         ` Jason Baron
2018-03-06 18:13           ` Michael S. Tsirkin
2018-03-08 12:48             ` Yan Vugenfirer
2018-03-02  3:56 ` [Qemu-devel] [PATCH 0/4] virtio-net: allow linkspeed and duplex setting no-reply
2018-03-02  3:56 ` no-reply
2018-03-02  3:58 ` no-reply
2018-03-02  3:59 ` no-reply
2018-03-02  4:24 ` no-reply
2018-03-02  4:25 ` no-reply

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=20180302221831-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=jbaron@akamai.com \
    --cc=qemu-devel@nongnu.org \
    --cc=virtio-dev@lists.oasis-open.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).