lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 15 Mar 2016 14:34:36 -0700
From:	Rick Jones <>
To:	Aaron Conole <>,,
	"Michael S. Tsirkin" <>,,
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
> 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