Thread (1 message) 1 message, 1 author, 2016-10-25

Re: [PATCH] virtio-net: Update the mtu code to match virtio spec

From: Aaron Conole <aconole@redhat.com>
Date: 2016-10-25 20:14:38
Also in: lkml

Aaron Conole [off-list ref] writes:
quoted
From: Aaron Conole <redacted>

The virtio committee recently ratified a change, VIRTIO-152, which
defines the mtu field to be 'max' MTU, not simply desired MTU.

This commit brings the virtio-net device in compliance with VIRTIO-152.

Additionally, drop the max_mtu branch - it cannot be taken since the u16
returned by virtio_cread16 will never exceed the initial value of
max_mtu.

Cc: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Jarod Wilson <redacted>
Signed-off-by: Aaron Conole <aconole@redhat.com>
---
Sorry about the subject line, David.  This is targetted at net-next, and
it appears my from was mangled.  Would you like me to resubmit with
these details corrected?
I answered my own question.  Sorry for the noise.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help