You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Section 5.1.6.2 Packet Transmission, subsection 5, states that:
“The header and packet are added as one output descriptor to the transmitq, and the device is notified of the new entry (see 5.1.5Device Initialization).
The following diff clarifies that the header and packet can be chained across multiple descriptors, in accordance with Section 2.6.4 Message Framing:
From: Gordon Stewart <[gordon@bedrocksystems.com](mailto:gordon@bedrocksystems.com)>
Date: Mon, 27 Feb 2023 13:59:45 -0500
Subject: [PATCH] 5.1.6.2 Packet Transmission; clarify "output descriptor"
---
device-types/net/description.tex | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/device-types/net/description.tex b/device-types/net/description.tex
index 0500bb6..98f0f20 100644
--- a/device-types/net/description.tex
+++ b/device-types/net/description.tex
@@ -487,8 +487,8 @@ \subsubsection{Packet Transmission}\label{sec:Device Types / Network Device / De
\item \field{num_buffers} is set to zero. This field is unused on transmitted packets.
-\item The header and packet are added as one output descriptor to the
- transmitq, and the device is notified of the new entry
+\item The header and packet output descriptors are added as one buffer to
+ the transmitq, and the device is notified of the new entry
(see \ref{sec:Device Types / Network Device / Device Initialization}~\nameref{sec:Device Types / Network Device / Device Initialization}).
\end{enumerate}
The text was updated successfully, but these errors were encountered:
https://lists.oasis-open.org/archives/virtio-comment/202302/msg00640.html
Section 5.1.6.2 Packet Transmission, subsection 5, states that:
“The header and packet are added as one output descriptor to the transmitq, and the device is notified of the new entry (see 5.1.5 Device Initialization).
The following diff clarifies that the header and packet can be chained across multiple descriptors, in accordance with Section 2.6.4 Message Framing:
The text was updated successfully, but these errors were encountered: