From: Victor Kaplansky <victork@redhat.com>
To: virtio-dev@lists.oasis-open.org
Cc: mst@redhat.com, jasowang@redhat.com, netdev@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: [PATCH v2 0/2] virtio-net: default_mtu - new conf. field
Date: Sun, 16 Aug 2015 16:42:15 +0300 [thread overview]
Message-ID: <1439732494-29765-1-git-send-email-victork@redhat.com> (raw)
This set of two patches adds a new field called default_mtu to
the configuration area of network devices. The motivation is to
allow libvirt to set initial MTU different from 1500 on guests
virtual NICs. We also propose to use this new field to report
MTU changes by the guest OS to the device to facilitate
debugging and mtu tunning.
The first patch just clarify the definition of existing fields in
network device configuration are. The second one adds default_mtu
and its description.
v2 changes:
* address comments by Michael S. Tsirkin:
- mac is driver-read-only.
- two status bits depend on different feature flags.
- use should/must only in conformance statements.
- rephrase "is set" -> "is offered" for features.
- other cosmetic changes.
- added conformance statements for a device and for a driver
regarding new 'default_mtu" field.
Victor Kaplansky (2):
virtio-net: rephrase devconf fields description
virtio-net: add default_mtu configuration field
content.tex | 67 +++++++++++++++++++++++++++++++++++++++++++++++++++----------
1 file changed, 56 insertions(+), 11 deletions(-)
--
--Victor
next reply other threads:[~2015-08-16 13:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-16 13:42 Victor Kaplansky [this message]
2015-08-16 13:42 ` [PATCH v2 1/2] virtio-net: rephrase devconf fields description Victor Kaplansky
2015-08-17 2:43 ` Jason Wang
2015-08-19 11:54 ` Victor Kaplansky
2015-08-20 2:46 ` Jason Wang
2015-08-16 13:42 ` [PATCH v2 2/2] virtio-net: add default_mtu configuration field Victor Kaplansky
2015-08-17 3:07 ` Jason Wang
2015-08-19 11:31 ` Victor Kaplansky
2015-08-20 2:48 ` Jason Wang
2015-08-20 19:31 ` Flavio Leitner
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=1439732494-29765-1-git-send-email-victork@redhat.com \
--to=victork@redhat.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtio-dev@lists.oasis-open.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).