Maxime Coquelin writes:
> On 09/04/2016 07:50 PM, Michael S. Tsirkin wrote:
>> On Sun, Sep 04, 2016 at 10:31:09AM -0400, Aaron Conole wrote:
>>> > It is helpful for a host to indicate an advisory MTU value to be set
>>> > on guest's NICs other than the assumed 1500
"Michael S. Tsirkin" writes:
> On Sun, Sep 04, 2016 at 08:50:57PM +0300, Michael S. Tsirkin wrote:
>> On Sun, Sep 04, 2016 at 10:31:09AM -0400, Aaron Conole wrote:
>> > It is helpful for a host to indicate an advisory MTU value to be set
>> > on guest's NICs other than the
On 09/04/2016 07:50 PM, Michael S. Tsirkin wrote:
On Sun, Sep 04, 2016 at 10:31:09AM -0400, Aaron Conole wrote:
> It is helpful for a host to indicate an advisory MTU value to be set
> on guest's NICs other than the assumed 1500 byte value.
This part of the description is wrong now.
It is no
On Sun, Sep 04, 2016 at 08:50:57PM +0300, Michael S. Tsirkin wrote:
> On Sun, Sep 04, 2016 at 10:31:09AM -0400, Aaron Conole wrote:
> > It is helpful for a host to indicate an advisory MTU value to be set
> > on guest's NICs other than the assumed 1500 byte value.
>
> This part of the description
On Sun, Sep 04, 2016 at 10:31:09AM -0400, Aaron Conole wrote:
> It is helpful for a host to indicate an advisory MTU value to be set
> on guest's NICs other than the assumed 1500 byte value.
This part of the description is wrong now.
It is no longer advisory and it should say "to indicate its MTU
It is helpful for a host to indicate an advisory MTU value to be set
on guest's 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.
The change adds a new field to