From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754373AbcDATcT (ORCPT ); Fri, 1 Apr 2016 15:32:19 -0400 Received: from mx1.redhat.com ([209.132.183.28]:39258 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751364AbcDATcS (ORCPT ); Fri, 1 Apr 2016 15:32:18 -0400 From: Aaron Conole To: netdev@vger.kernel.org, "Michael S. Tsirkin" , virtualization@lists.linux-foundation.org, linux-kernel@vger.kernel.org, Paolo Abeni , Sergei Shtylyov , Pankaj Gupta Subject: [RFC v3 -next 0/2] virtio-net: Advised MTU feature Date: Fri, 1 Apr 2016 15:32:14 -0400 Message-Id: <1459539136-13948-1-git-send-email-aconole@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The following series adds the ability for a hypervisor to set an MTU on the guest during feature negotiation phase. This is useful for VM orchestration when, for instance, tunneling is involved and the MTU of the various systems should be homogenous. The first patch adds the feature bit as described in the proposed VIRTIO spec addition found at https://lists.oasis-open.org/archives/virtio-dev/201603/msg00001.html The second patch adds a user of the bit, and a warning when the guest changes the MTU from the hypervisor advised MTU. Future patches may add more thorough error handling. v2: * Whitespace and code style cleanups from Sergei Shtylyov and Paolo Abeni * Additional test before printing a warning v3: * Removed the warning when changing MTU (which simplified the code) Aaron Conole (2): virtio: Start feature MTU support virtio_net: Read the advised MTU drivers/net/virtio_net.c | 8 ++++++++ include/uapi/linux/virtio_net.h | 3 +++ 2 files changed, 11 insertions(+) -- 2.5.5