Section like "Advice" is not the current practice. Lets capture such
advice as notes.
Signed-off-by: Parav Pandit <pa...@nvidia.com>
---
device-types/net/description.tex | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/device-types/net/description.tex b/device-types/net/description.tex
index 68311ab..a8dff97 100644
--- a/device-types/net/description.tex
+++ b/device-types/net/description.tex
@@ -1090,7 +1090,7 @@ \subsubsection{Processing of Incoming
Packets}\label{sec:Device Types / Network
\hline
\end{tabular}
-\subparagraph{Advice}
+\begin{note}
Example uses of the inner header hash:
\begin{itemize}
\item Legacy tunneling protocols, lacking the outer header entropy, can use
RSS with the inner header hash to
@@ -1105,6 +1105,8 @@ \subsubsection{Processing of Incoming
Packets}\label{sec:Device Types / Network
Besides disabling the inner header hash, mitigations would depend on how the
hash is used. When the hash
use is limited to the RSS queue selection, the inner header hash may have
quality of service (QoS) limitations.
+\end{note}
+
\devicenormative{\subparagraph}{Inner Header Hash}{Device Types / Network
Device / Device Operation / Control Virtqueue / Inner Header Hash}
If the (outer) header of the received packet does not match any encapsulation
types enabled
--
2.26.2
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-h...@lists.oasis-open.org
