From: "Daniel P. Berrange" <berrange@redhat.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: mst@redhat.com, aconole@redhat.com, pbonzini@redhat.com,
qemu-devel@nongnu.org, jasowang@redhat.com,
yuanhan.liu@linux.intel.com, fbl@redhat.com, mlureau@redhat.com,
ktraynor@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4 0/3] virtio-net: Add support to MTU feature
Date: Mon, 12 Dec 2016 10:34:32 +0000 [thread overview]
Message-ID: <20161212103432.GH15611@redhat.com> (raw)
In-Reply-To: <cc475d20-6e77-17ab-b41e-56a6d4bf81b2@redhat.com>
On Mon, Dec 12, 2016 at 11:12:56AM +0100, Maxime Coquelin wrote:
> Hi Daniel,
>
> On 12/12/2016 11:02 AM, Daniel P. Berrange wrote:
> > On Sat, Dec 10, 2016 at 04:30:35PM +0100, Maxime Coquelin wrote:
> > > Thanks for the reviews,
> > >
> > > This series implements Virtio spec update from Aaron Conole which
> > > defines a way for the host to expose its max MTU to the guest.
> > >
> > > "host_mtu" parameter is added to provide QEMU with the MTU value,
> > > and the backend, if supported, gets notified of the MTU value when the
> > > MTU feature neogotiation succeeds.
> > >
> > > Only user backend currently supports MTU notification. A new protocol
> > > feature has been implemented for sending MTU value to the backend.
> > >
> > > For kernel backend, it is expected the management tool also configures
> > > the tap/macvtap interface with same MTU value.
> > > Daniel, I would be interrested about your feedback on this implementation
> > > from management tool point of view.
> >
> > I can't give real feedback yet, as I'm not seeing clear information on
> > what problem this series is designed to solve....
>
> Right, I agree it is missing a bit of context here, I'll add more about
> the background in next revision.
>
> The goal of this series is to address two things:
> 1. Providing a way for the guests to use the same MTU as the host,
> in order to have a consistent MTU value across the infrastructure.
Ok, currently libvirt sets the MTU of the tap device based on the MTU
of the device it will be attached to. This change means we need to pass
that MTU value into QEMU via the -netdev command line so it can inform
the guest what the MTU is.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://entangle-photo.org -o- http://search.cpan.org/~danberr/ :|
next prev parent reply other threads:[~2016-12-12 10:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-10 15:30 [Qemu-devel] [PATCH v4 0/3] virtio-net: Add support to MTU feature Maxime Coquelin
2016-12-10 15:30 ` [Qemu-devel] [PATCH v4 1/3] vhost-user: Add MTU protocol feature and op Maxime Coquelin
2016-12-10 15:30 ` [Qemu-devel] [PATCH v4 2/3] vhost-net: Notify the backend about the host MTU Maxime Coquelin
2016-12-10 15:30 ` [Qemu-devel] [PATCH v4 3/3] virtio-net: Add MTU feature support Maxime Coquelin
2016-12-12 10:02 ` [Qemu-devel] [PATCH v4 0/3] virtio-net: Add support to MTU feature Daniel P. Berrange
2016-12-12 10:12 ` Maxime Coquelin
2016-12-12 10:34 ` Daniel P. Berrange [this message]
2016-12-13 13:04 ` Maxime Coquelin
2016-12-13 13:07 ` Daniel P. Berrange
2016-12-13 13:17 ` Maxime Coquelin
2017-01-10 3:43 ` Michael S. Tsirkin
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=20161212103432.GH15611@redhat.com \
--to=berrange@redhat.com \
--cc=aconole@redhat.com \
--cc=fbl@redhat.com \
--cc=jasowang@redhat.com \
--cc=ktraynor@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=mlureau@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yuanhan.liu@linux.intel.com \
/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).