[OASIS Issue Tracker] (VIRTIO-152) exposing host MTU to guest

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/VIRTIO-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael S. Tsirkin updated VIRTIO-152:
--------------------------------------

    Resolution: 
virtio-net: add Max MTU configuration field
    
It is helpful for a host to indicate it's MTU to be set on guest NICs other than the assumed 1500 byte value.  This helps in situations where the host network is using Jumbo Frames, or aiding in PMTU discovery by configuring a homogenous network.  It is also helpful for sizing receive buffers correctly.
   
The change adds a new field to configuration area of network  devices.  It will be used to pass a maximum MTU from the device to the driver.  This will be used by the driver as a maximum value for packet sizes during transmission, without segmentation offloading.
    
    In addition, in order to support backward and forward compatibility,   we introduce a new feature bit called VIRTIO_NET_F_MTU.

    git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio/trunk@585 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652


> exposing host MTU to guest
> --------------------------
>
>                 Key: VIRTIO-152
>                 URL: https://issues.oasis-open.org/browse/VIRTIO-152
>             Project: OASIS Virtual I/O Device (VIRTIO) TC
>          Issue Type: New Feature
>    Affects Versions: virtio 1.0 cs04
>         Environment: Aaron Conole <aconole@redhat.com>
>            Reporter: Michael S. Tsirkin
>            Priority: Minor
>             Fix For: virtio 1.1 cs01
>
>
> It is helpful for a host to indicate its MTU value to the guest.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)