From: Cyril Germond <cgermond@kalray.eu>
To: virtio-comment@lists.oasis-open.org
Subject: [virtio-comment] [PATCH] virtio-net : Fix virtio_net_hdr struct size when VIRTIO_NET_F_HASH_REPORT feature is negociated.
Date: Thu, 4 Aug 2022 19:37:30 +0200 (CEST) [thread overview]
Message-ID: <001a01d8a828$df564200$9e02c600$@kalray.eu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2155 bytes --]
content.tex | 4 ++--
split-ring.tex | 6 +++---
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/content.tex b/content.tex
index e863709..263cb05 100644
--- a/content.tex
+++ b/content.tex
@@ -3620,8 +3620,8 @@ \subsubsection{Setting Up Receive
Buffers}\label{sec:Device Types / Network Devi
features are used, the maximum incoming packet
will be to 65550 bytes long (the maximum size of a
TCP or UDP packet, plus the 14 byte ethernet header), otherwise
-1514 bytes. The 12-byte struct virtio_net_hdr is prepended to this,
-making for 65562 or 1526 bytes.
+1514 bytes. The 12-byte (or 16-byte if VIRTIO_NET_F_HASH_REPORT feature
has been negotiated) struct virtio_net_hdr is prepended to this,
+making for 65562 or 1526 bytes (respectively 65566 and 1530 bytes if
VIRTIO_NET_F_HASH_REPORT has been negotiated).
\drivernormative{\paragraph}{Setting Up Receive Buffers}{Device Types /
Network Device / Device Operation / Setting Up Receive Buffers}
diff --git a/split-ring.tex b/split-ring.tex
index de94038..e6953d7 100644
--- a/split-ring.tex
+++ b/split-ring.tex
@@ -128,10 +128,10 @@ \subsection{Legacy Interfaces: A Note on Virtqueue
Endianness}\label{sec:Basic F
\subsection{Message Framing}\label{sec:Basic Facilities of a Virtio Device
/ Virtqueues / Message Framing}
The framing of messages with descriptors is
independent of the contents of the buffers. For example, a network
-transmit buffer consists of a 12 byte header followed by the network
+transmit buffer consists of a 12 (or 16 if VIRTIO_NET_F_HASH_REPORT
feature has been negociated) byte header followed by the network
packet. This could be most simply placed in the descriptor table as a
-12 byte output descriptor followed by a 1514 byte output descriptor,
-but it could also consist of a single 1526 byte output descriptor in
+12 (or 16) byte output descriptor followed by a 1514 byte output
descriptor,
+but it could also consist of a single 1526 (or 1530) byte output
descriptor in
the case where the header and packet are adjacent, or even three or
more descriptors (possibly with loss of efficiency in that case).
[-- Attachment #2: Type: text/html, Size: 4508 bytes --]
next reply other threads:[~2022-08-04 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 17:37 Cyril Germond [this message]
2022-08-04 19:24 ` [virtio-comment] [PATCH] virtio-net : Fix virtio_net_hdr struct size when VIRTIO_NET_F_HASH_REPORT feature is negociated Alvaro Karsz
2022-08-05 6:35 ` Cyril Germond
2022-08-09 11:50 ` Cornelia Huck
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='001a01d8a828$df564200$9e02c600$@kalray.eu' \
--to=cgermond@kalray.eu \
--cc=virtio-comment@lists.oasis-open.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