On Mon, Aug 17, 2015 at 10:43:46AM +0800, Jason Wang wrote:
On 08/16/2015 09:42 PM, Victor Kaplansky wrote:
Clarify general description of the mac, status and
max_virtqueue_pairs fields. Specifically, the old description is
vague about configuration layout and fields offsets when some
On Mon, Aug 17, 2015 at 11:07:15AM +0800, Jason Wang wrote:
On 08/16/2015 09:42 PM, Victor Kaplansky wrote:
@@ -3128,6 +3134,7 @@ struct virtio_net_config {
u8 mac[6];
le16 status;
le16 max_virtqueue_pairs;
+le16 default_mtu;
Looks like mtu
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
.
Signed-off-by: Victor Kaplansky vict...@redhat.com
---
content.tex | 42 +++---
1 file changed, 31 insertions(+), 11 deletions(-)
diff --git a/content.tex b/content.tex
index d989d98..342183b 100644
--- a/content.tex
+++ b/content.tex
@@ -3115,23 +3115,14 @@ were
to the device
when a new MTU is assigned by the guest OS.
In addition, in order to support backward and forward
compatibility, we introduce a new feature bit called
VIRTIO_NET_F_DEFAULT_MTU.
Added conformance statements for a device and a driver.
Signed-off-by: Victor Kaplansky vict...@redhat.com
