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.... 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/ :|
