[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56E87FEC.2030600@hpe.com>
Date: Tue, 15 Mar 2016 14:34:36 -0700
From: Rick Jones <rick.jones2@....com>
To: Aaron Conole <aconole@...hat.com>, netdev@...r.kernel.org,
"Michael S. Tsirkin" <mst@...hat.com>,
virtualization@...ts.linux-foundation.org,
linux-kernel@...r.kernel.org
Subject: Re: [RFC v2 -next 0/2] virtio-net: Advised MTU feature
On 03/15/2016 02:04 PM, Aaron Conole wrote:
> The following series adds the ability for a hypervisor to set an MTU on the
> guest during feature negotiation phase. This is useful for VM orchestration
> when, for instance, tunneling is involved and the MTU of the various systems
> should be homogenous.
>
> The first patch adds the feature bit as described in the proposed VFIO spec
> addition found at
> https://lists.oasis-open.org/archives/virtio-dev/201603/msg00001.html
>
> The second patch adds a user of the bit, and a warning when the guest changes
> the MTU from the hypervisor advised MTU. Future patches may add more thorough
> error handling.
How do you see this interacting with VMs getting MTU settings via DHCP?
rick jones
>
> v2:
> * Whitespace and code style cleanups from Sergei Shtylyov and Paolo Abeni
> * Additional test before printing a warning
>
> Aaron Conole (2):
> virtio: Start feature MTU support
> virtio_net: Read the advised MTU
>
> drivers/net/virtio_net.c | 12 ++++++++++++
> include/uapi/linux/virtio_net.h | 3 +++
> 2 files changed, 15 insertions(+)
>
Powered by blists - more mailing lists