From: Rick Jones <rick.jones2@hpe.com>
To: Aaron Conole <aconole@redhat.com>,
netdev@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC v2 -next 0/2] virtio-net: Advised MTU feature
Date: Tue, 15 Mar 2016 14:34:36 -0700 [thread overview]
Message-ID: <56E87FEC.2030600@hpe.com> (raw)
In-Reply-To: <1458075853-14789-1-git-send-email-aconole@redhat.com>
On 03/15/2016 02:04 PM, Aaron Conole wrote:
> 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 VFIO 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.
How do you see this interacting with VMs getting MTU settings via DHCP?
rick jones
>
> v2:
> * Whitespace and code style cleanups from Sergei Shtylyov and Paolo Abeni
> * Additional test before printing a warning
>
> Aaron Conole (2):
> virtio: Start feature MTU support
> virtio_net: Read the advised MTU
>
> drivers/net/virtio_net.c | 12 ++++++++++++
> include/uapi/linux/virtio_net.h | 3 +++
> 2 files changed, 15 insertions(+)
>
next prev parent reply other threads:[~2016-03-15 21:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 21:04 [RFC v2 -next 0/2] virtio-net: Advised MTU feature Aaron Conole
2016-03-15 21:04 ` [RFC v2 -next 1/2] virtio: Start feature MTU support Aaron Conole
2016-03-16 18:23 ` Stephen Hemminger
2016-03-16 18:23 ` Stephen Hemminger
2016-03-16 18:29 ` Michael S. Tsirkin
2016-03-16 18:29 ` Michael S. Tsirkin
2016-03-17 21:10 ` Aaron Conole
2016-03-17 21:10 ` Aaron Conole
2016-03-17 22:04 ` Stephen Hemminger
2016-03-17 22:04 ` Stephen Hemminger
2016-03-15 21:04 ` [RFC v2 -next 2/2] virtio_net: Read the advised MTU Aaron Conole
2016-03-16 14:11 ` Sergei Shtylyov
2016-03-17 21:15 ` Aaron Conole
2016-03-17 21:15 ` Aaron Conole
2016-03-16 14:24 ` Michael S. Tsirkin
2016-03-16 14:24 ` Michael S. Tsirkin
2016-03-17 21:20 ` Aaron Conole
2016-03-17 21:20 ` Aaron Conole
2016-03-15 21:34 ` Rick Jones [this message]
2016-03-17 21:24 ` [RFC v2 -next 0/2] virtio-net: Advised MTU feature Aaron Conole
2016-03-17 21:24 ` Aaron Conole
2016-03-16 4:55 ` Pankaj Gupta
2016-03-16 4:55 ` Pankaj Gupta
2016-03-17 21:24 ` Aaron Conole
2016-03-17 21:24 ` Aaron Conole
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56E87FEC.2030600@hpe.com \
--to=rick.jones2@hpe.com \
--cc=aconole@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.