[lkml]   [2016]   [Oct]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] virtio-net: Update the mtu code to match virtio spec
Aaron Conole <> writes:

>> From: Aaron Conole <>
>> 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" <>
>> Cc: Jarod Wilson <>
>> Signed-off-by: Aaron Conole <>
>> ---
> 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.

 \ /
  Last update: 2016-10-25 22:15    [W:0.040 / U:0.196 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site