search for: default_mac

...e: > > @@ -3128,6 +3134,7 @@ struct virtio_net_config { > > u8 mac[6]; > > le16 status; > > le16 max_virtqueue_pairs; > > + le16 default_mtu; > > Looks like "mtu" is ok, consider we use "mac" instead of "default_mac". Good point. I'll change the name in the next version of the patch. > > > }; > > \end{lstlisting} > > > > @@ -3158,6 +3165,15 @@ by the driver after negotiation. > > \field{max_virtqueue_pairs} is valid only if VIRTIO_NET_F_MQ is > >...

...e: > > @@ -3128,6 +3134,7 @@ struct virtio_net_config { > > u8 mac[6]; > > le16 status; > > le16 max_virtqueue_pairs; > > + le16 default_mtu; > > Looks like "mtu" is ok, consider we use "mac" instead of "default_mac". Good point. I'll change the name in the next version of the patch. > > > }; > > \end{lstlisting} > > > > @@ -3158,6 +3165,15 @@ by the driver after negotiation. > > \field{max_virtqueue_pairs} is valid only if VIRTIO_NET_F_MQ is > >...

...ture bits / Feature bit requirements} > @@ -3128,6 +3134,7 @@ struct virtio_net_config { > u8 mac[6]; > le16 status; > le16 max_virtqueue_pairs; > + le16 default_mtu; Looks like "mtu" is ok, consider we use "mac" instead of "default_mac". > }; > \end{lstlisting} > > @@ -3158,6 +3165,15 @@ by the driver after negotiation. > \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...

...t; @@ -3128,6 +3134,7 @@ struct virtio_net_config { >>> u8 mac[6]; >>> le16 status; >>> le16 max_virtqueue_pairs; >>> + le16 default_mtu; >> Looks like "mtu" is ok, consider we use "mac" instead of "default_mac". > Good point. I'll change the name in the next version of the patch. > >>> }; >>> \end{lstlisting} >>> >>> @@ -3158,6 +3165,15 @@ by the driver after negotiation. >>> \field{max_virtqueue_pairs} is valid only if VIRTIO_NET_F_MQ...

Sometimes it is essential for libvirt to be able to configure MTU on guest's NICs to a value different from 1500. The change adds a new field to configuration 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

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

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