search for: virtio_net_f_default_mtu

This set of two patches adds a new field called default_mtu to the configuration area of network devices. The motivation is to allow libvirt to set initial MTU different from 1500 on guests virtual NICs. We also propose to use this new field to report MTU changes by the guest OS to the device to facilitate debugging and mtu tunning. The first patch just clarify the definition of existing fields

...tion area of network devices. It will be used to pass initial MTU from the device to the driver, and to pass modified MTU from driver to the device when a new MTU is assigned by the guest OS. In addition, in order to support backward and forward compatibility, we introduce a new feature bit called VIRTIO_NET_F_DEFAULT_MTU. Added conformance statements for a device and a driver. Signed-off-by: Victor Kaplansky <victork at redhat.com> Signed-off-by: Victor Kaplansky <victork at redhat.com> --- content.tex | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/content.tex b/c...

This set of two patches adds a new field called default_mtu to the configuration area of network devices. The motivation is to allow libvirt to set initial MTU different from 1500 on guests virtual NICs. We also propose to use this new field to report MTU changes by the guest OS to the device to facilitate debugging and mtu tunning. The first patch just clarify the definition of existing fields

...It will be used to pass initial MTU from the device to > the driver, and to pass modified MTU from driver to the device > when a new MTU is assigned by the guest OS. > > In addition, in order to support backward and forward > compatibility, we introduce a new feature bit called > VIRTIO_NET_F_DEFAULT_MTU. > > Added conformance statements for a device and a driver. > > Signed-off-by: Victor Kaplansky <victork at redhat.com> > > Signed-off-by: Victor Kaplansky <victork at redhat.com> > --- > content.tex | 25 +++++++++++++++++++++++++ > 1 file changed, 25 i...

...> > \field{max_virtqueue_pairs} is valid only if VIRTIO_NET_F_MQ is > > set and can be read by the driver. > > > > +\item [\field{default_mtu}] is a hint to the driver set by the > > + device. It is valid during feature negotiation only if > > + VIRTIO_NET_F_DEFAULT_MTU is offered and holds the initial value > > + of MTU to be used by the driver. If VIRTIO_NET_F_DEFAULT_MTU is > > + negotiated, the driver uses the \field{default_mtu} as an initial > > + value, and also reports MTU changes to the device by writes to > > + \field{...

...> > \field{max_virtqueue_pairs} is valid only if VIRTIO_NET_F_MQ is > > set and can be read by the driver. > > > > +\item [\field{default_mtu}] is a hint to the driver set by the > > + device. It is valid during feature negotiation only if > > + VIRTIO_NET_F_DEFAULT_MTU is offered and holds the initial value > > + of MTU to be used by the driver. If VIRTIO_NET_F_DEFAULT_MTU is > > + negotiated, the driver uses the \field{default_mtu} as an initial > > + value, and also reports MTU changes to the device by writes to > > + \field{...

...\field{max_virtqueue_pairs} is valid only if VIRTIO_NET_F_MQ is >>> set and can be read by the driver. >>> >>> +\item [\field{default_mtu}] is a hint to the driver set by the >>> + device. It is valid during feature negotiation only if >>> + VIRTIO_NET_F_DEFAULT_MTU is offered and holds the initial value >>> + of MTU to be used by the driver. If VIRTIO_NET_F_DEFAULT_MTU is >>> + negotiated, the driver uses the \field{default_mtu} as an initial >>> + value, and also reports MTU changes to the device by writes to >>>...