Short document fixes to inner hash feature
cover Short document fixes to inner hash feature
This short patches fixes the editing errors that stops the pdf and html generation.
These 3 fixes are for the patch [1] for the github issue [2].
[1] https://lists.oasis-open.org/archives/virtio-comment/202307/msg00024.html
[2] https://github.com/oasis-tcs/virtio-spec/issues/173
Patch summary:
patch-1 place C code under listing
patch-2 avoid hyphen and extra braces
patch-3 use table as hyperlink do not work well in C code listing patch-4 refer 'advice' as 'note'
Patch 1 to 3 appears to be must in the testing.
Patch 4 is not a fix and can be done later if it requires discussion.
Parav Pandit (4):
virtio-net: Place C code under listing
virtio-net: Avoid hyphen and extra braces
virtio-net: Use table to describe inner hash to rfc mapping
virtio-net: Use note instead of advice
device-types/net/description.tex | 45 ++++++++++++++++++++++---------- introduction.tex | 15 +++++------ 2 files changed, 38 insertions(+), 22 deletions(-)
Signature · 6 lines
2.26.2 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
PATCH 1/4 virtio-net: Place C code under listing
With extra white space for the define, pdf generation fails. Also place the C code under listing.
--- device-types/net/description.tex | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
device-types/net/description.tex +3 -1
@@ -1024,12 +1024,14 @@ \subsubsection{Processing of Incoming Packets}\label{sec:Device Types / Network If VIRTIO_NET_F_HASH_TUNNEL has been negotiated, the driver can send the command VIRTIO_NET_CTRL_HASH_TUNNEL_SET to configure the calculation of the inner header hash. +\begin{lstlisting} struct virtnet_hash_tunnel { le32 enabled_tunnel_types; }; #define VIRTIO_NET_CTRL_HASH_TUNNEL 7 - #define VIRTIO_NET_CTRL_HASH_TUNNEL_SET 0 +#define VIRTIO_NET_CTRL_HASH_TUNNEL_SET 0 +\end{lstlisting} Field \field{enabled_tunnel_types} contains the bitmask of encapsulation types enabled for inner header hash. See \ref{sec:Device Types / Network Device / Device Operation / Processing of Incoming Packets /
Signature · 18 lines
2.26.2 This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC. In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting. Subscribe: [email protected] Unsubscribe: [email protected] List help: [email protected] List archive: https://lists.oasis-open.org/archives/virtio-comment/ Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists Committee: https://www.oasis-open.org/committees/virtio/ Join OASIS: https://www.oasis-open.org/join/
Re: [virtio-comment] [PATCH 1/4] virtio-net: Place C code under listing
Quoted 14 lines · Parav Pandit
With extra white space for the define, pdf generation fails. Also place the C code under listing.
Signed-off-by Parav Pandit <[email protected]>--- device-types/net/description.tex | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)device-types/net/description.tex +0
-0@@ -1024,12 +1024,14 @@ \subsubsection{Processing of Incoming Packets}\label{sec:Device Types / Network If VIRTIO_NET_F_HASH_TUNNEL has been negotiated, the driver can send the command
device-types/net/description.tex \subsubsection{Processing of Incoming Packets}\label{sec:Device Types / Network · line 1033
Quoted 10 lines
device-types/net/description.tex +2
-1VIRTIO_NET_CTRL_HASH_TUNNEL_SET to configure the calculation of the inner header hash. +\begin{lstlisting} struct virtnet_hash_tunnel { le32 enabled_tunnel_types; }; #define VIRTIO_NET_CTRL_HASH_TUNNEL 7 - #define VIRTIO_NET_CTRL_HASH_TUNNEL_SET 0 +#define VIRTIO_NET_CTRL_HASH_TUNNEL_SET 0
I think the indentation here is intentional (as in other, similare sections.)
device-types/net/description.tex \subsubsection{Processing of Incoming Packets}\label{sec:Device Types / Network · line 1037
Quoted 4 lines
device-types/net/description.tex +1
-0+\end{lstlisting} Field \field{enabled_tunnel_types} contains the bitmask of encapsulation types enabled for inner header hash. See \ref{sec:Device Types / Network Device / Device Operation / Processing of Incoming Packets /
This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting.
Subscribe: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
RE: [virtio-comment] [PATCH 1/4] virtio-net: Place C code under listing
Quoted 32 lines
From: Cornelia Huck <[email protected]>
Sent: Thursday, July 13, 2023 5:13 AM
To: Parav Pandit <[email protected]>; [email protected]; [email protected]Quoted 14 lines · Parav Pandit
With extra white space for the define, pdf generation fails. Also place the C code under listing.
Signed-off-by Parav Pandit <[email protected]>--- device-types/net/description.tex | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)device-types/net/description.tex +0
-0@@ -1024,12 +1024,14 @@ \subsubsection{Processing of IncomingQuoted 2 lines
Packets}\label{sec:Device Types / Network If
VIRTIO_NET_F_HASH_TUNNELhas been negotiated, the driver can send the command
VIRTIO_NET_CTRL_HASH_TUNNEL_SETto configure the calculation of the inner header hash.Quoted 6 lines
+\begin{lstlisting}
struct virtnet_hash_tunnel { le32 enabled_tunnel_types;};
Quoted 7 lines
Quoted 3 lines
#define
VIRTIO_NET_CTRL_HASH_TUNNEL7
- #defineVIRTIO_NET_CTRL_HASH_TUNNEL_SET0
+#defineVIRTIO_NET_CTRL_HASH_TUNNEL_SET0I think the indentation here is intentional (as in other, similare sections.)
Oh right. It is the command part.
Quoted 6 lines
Quoted 3 lines
+\end{lstlisting}
Field \field{enabled_tunnel_types} contains the bitmask of encapsulation
types enabled for inner header hash.
Quoted 2 lines
See \ref{sec:Device Types / Network Device / Device Operation /
Processing of Incoming Packets /
This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting.
Subscribe: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
PATCH 2/4 virtio-net: Avoid hyphen and extra braces
In reply to Parav PanditAvoid hyphen and replace it with white space like rest of the entries. Also avoid unnecessary braces.
Name RFC as just RFC without special prefix about it.
This likely resolves the html generation errors.
--- device-types/net/description.tex | 2 +- introduction.tex | 15 +++++++-------- 2 files changed, 8 insertions(+), 9 deletions(-)
device-types/net/description.tex +1 -1
@@ -904,7 +904,7 @@ \subsubsection{Processing of Incoming Packets}\label{sec:Device Types / Network \end{itemize} The per-packet hash calculation can depend on the IP packet type. See -\hyperref[intro:IP]{[IP]}, \hyperref[intro:UDP]{[UDP]} and \hyperref[intro:TCP]{[TCP]}. +\hyperref[intro:IP]{IP}, \hyperref[intro:UDP]{UDP} and \hyperref[intro:TCP]{TCP}. \subparagraph{Supported/enabled hash types} \label{sec:Device Types / Network Device / Device Operation / Processing of Incoming Packets / Hash calculation for incoming packets / Supported/enabled hash types}
introduction.tex +7 -8
@@ -101,26 +101,25 @@ \section{Normative References}\label{sec:Normative References} \phantomsection\label{intro:SEC1}\textbf{[SEC1]} & Standards for Efficient Cryptography Group(SECG), ``SEC1: Elliptic Cureve Cryptography'', Version 1.0, September 2000. \newline\url{https://www.secg.org/sec1-v2.pdf}\\ - - \phantomsection\label{intro:gre_rfc2784}\textbf{[GRE_rfc2784]} & + \phantomsection\label{intro:rfc2784}\textbf{[RFC2784]} & Generic Routing Encapsulation. This protocol is only specified for IPv4 and used as either the payload or delivery protocol. \newline\url{https://datatracker.ietf.org/doc/rfc2784/}\\ - \phantomsection\label{intro:gre_rfc2890}\textbf{[GRE_rfc2890]} & - Key and Sequence Number Extensions to GRE \ref{intro:gre_rfc2784}. This protocol describes extensions by which two fields, Key and - Sequence Number, can be optionally carried in the GRE Header \ref{intro:gre_rfc2784}. + \phantomsection\label{intro:rfc2890}\textbf{[RFC2890]} & + Key and Sequence Number Extensions to GRE \ref{intro:rfc2784}. This protocol describes extensions by which two fields, Key and + Sequence Number, can be optionally carried in the GRE Header \ref{intro:rfc2784}. \newline\url{https://www.rfc-editor.org/rfc/rfc2890}\\ - \phantomsection\label{intro:gre_rfc7676}\textbf{[GRE_rfc7676]} & + \phantomsection\label{intro:rfc7676}\textbf{[RFC7676]} & IPv6 Support for Generic Routing Encapsulation (GRE). This protocol is specified for IPv6 and used as either the payload or delivery protocol. Note that this does not change the GRE header format or any behaviors specified by RFC 2784 or RFC 2890. \newline\url{https://datatracker.ietf.org/doc/rfc7676/}\\ - \phantomsection\label{intro:gre_in_udp_rfc8086}\textbf{[GRE-in-UDP]} & + \phantomsection\label{intro:rfc8086}\textbf{[GRE in UDP]} & GRE-in-UDP Encapsulation. This specifies a method of encapsulating network protocol packets within GRE and UDP headers. This protocol is specified for IPv4 and IPv6, and used as either the payload or delivery protocol. \newline\url{https://www.rfc-editor.org/rfc/rfc8086}\\ \phantomsection\label{intro:vxlan}\textbf{[VXLAN]} & Virtual eXtensible Local Area Network. \newline\url{https://datatracker.ietf.org/doc/rfc7348/}\\ - \phantomsection\label{intro:vxlan-gpe}\textbf{[VXLAN-GPE]} & + \phantomsection\label{intro:vxlan gpe}\textbf{[VXLAN GPE]} & Generic Protocol Extension for VXLAN. This protocol describes extending Virtual eXtensible Local Area Network (VXLAN) via changes to the VXLAN header. \newline\url{https://www.ietf.org/archive/id/draft-ietf-nvo3-vxlan-gpe-12.txt}\\ \phantomsection\label{intro:geneve}\textbf{[GENEVE]} &
Signature · 18 lines
2.26.2 This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC. In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting. Subscribe: [email protected] Unsubscribe: [email protected] List help: [email protected] List archive: https://lists.oasis-open.org/archives/virtio-comment/ Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists Committee: https://www.oasis-open.org/committees/virtio/ Join OASIS: https://www.oasis-open.org/join/
[virtio-comment] Re: [PATCH 2/4] virtio-net: Avoid hyphen and extra braces
Quoted 17 lines · Parav Pandit
Avoid hyphen and replace it with white space like rest of the entries. Also avoid unnecessary braces.
Name RFC as just RFC without special prefix about it.This likely resolves the html generation errors.
Signed-off-by Parav Pandit <[email protected]>--- device-types/net/description.tex | 2 +- introduction.tex | 15 +++++++-------- 2 files changed, 8 insertions(+), 9 deletions(-)device-types/net/description.tex +0
-0
device-types/net/description.tex \subsubsection{Processing of Incoming Packets}\label{sec:Device Types / Network · line 907
Quoted 5 lines
device-types/net/description.tex +1
-1@@ -904,7 +904,7 @@ \subsubsection{Processing of Incoming Packets}\label{sec:Device Types / Network \end{itemize} The per-packet hash calculation can depend on the IP packet type. See -\hyperref[intro:IP]{[IP]}, \hyperref[intro:UDP]{[UDP]} and \hyperref[intro:TCP]{[TCP]}. +\hyperref[intro:IP]{IP}, \hyperref[intro:UDP]{UDP} and \hyperref[intro:TCP]{TCP}.
I'd keep that as-is (I think it looks nicer with the brackets).
Quoted 20 lines
device-types/net/description.tex +0
-0\subparagraph{Supported/enabled hash types} \label{sec:Device Types / Network Device / Device Operation / Processing of Incoming Packets / Hash calculation for incoming packets / Supported/enabled hash types}introduction.tex +2
-5@@ -101,26 +101,25 @@ \section{Normative References}\label{sec:Normative References} \phantomsection\label{intro:SEC1}\textbf{[SEC1]} & Standards for Efficient Cryptography Group(SECG), ``SEC1: Elliptic Cureve Cryptography'', Version 1.0, September 2000. \newline\url{https://www.secg.org/sec1-v2.pdf}\\ - - \phantomsection\label{intro:gre_rfc2784}\textbf{[GRE_rfc2784]} & + \phantomsection\label{intro:rfc2784}\textbf{[RFC2784]} & Generic Routing Encapsulation. This protocol is only specified for IPv4 and used as either the payload or delivery protocol. \newline\url{https://datatracker.ietf.org/doc/rfc2784/}\\ - \phantomsection\label{intro:gre_rfc2890}\textbf{[GRE_rfc2890]} & - Key and Sequence Number Extensions to GRE \ref{intro:gre_rfc2784}. This protocol describes extensions by which two fields, Key and - Sequence Number, can be optionally carried in the GRE Header \ref{intro:gre_rfc2784}. + \phantomsection\label{intro:rfc2890}\textbf{[RFC2890]} &
introduction.tex \section{Normative References}\label{sec:Normative References} · line 115
Quoted 10 lines
introduction.tex +4
-2+ Key and Sequence Number Extensions to GRE \ref{intro:rfc2784}. This protocol describes extensions by which two fields, Key and + Sequence Number, can be optionally carried in the GRE Header \ref{intro:rfc2784}. \newline\url{https://www.rfc-editor.org/rfc/rfc2890}\\ - \phantomsection\label{intro:gre_rfc7676}\textbf{[GRE_rfc7676]} & + \phantomsection\label{intro:rfc7676}\textbf{[RFC7676]} & IPv6 Support for Generic Routing Encapsulation (GRE). This protocol is specified for IPv6 and used as either the payload or delivery protocol. Note that this does not change the GRE header format or any behaviors specified by RFC 2784 or RFC 2890. \newline\url{https://datatracker.ietf.org/doc/rfc7676/}\\ - \phantomsection\label{intro:gre_in_udp_rfc8086}\textbf{[GRE-in-UDP]} & + \phantomsection\label{intro:rfc8086}\textbf{[GRE in UDP]} &
Hyphens are ok, I'd keep it.
introduction.tex \section{Normative References}\label{sec:Normative References} · line 125
Quoted 11 lines
introduction.tex +1
-1GRE-in-UDP Encapsulation. This specifies a method of encapsulating network protocol packets within GRE and UDP headers. This protocol is specified for IPv4 and IPv6, and used as either the payload or delivery protocol. \newline\url{https://www.rfc-editor.org/rfc/rfc8086}\\ \phantomsection\label{intro:vxlan}\textbf{[VXLAN]} & Virtual eXtensible Local Area Network. \newline\url{https://datatracker.ietf.org/doc/rfc7348/}\\ - \phantomsection\label{intro:vxlan-gpe}\textbf{[VXLAN-GPE]} & + \phantomsection\label{intro:vxlan gpe}\textbf{[VXLAN GPE]} & Generic Protocol Extension for VXLAN. This protocol describes extending Virtual eXtensible Local Area Network (VXLAN) via changes to the VXLAN header. \newline\url{https://www.ietf.org/archive/id/draft-ietf-nvo3-vxlan-gpe-12.txt}\\ \phantomsection\label{intro:geneve}\textbf{[GENEVE]} &
This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting.
Subscribe: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
PATCH 3/4 virtio-net: Use table to describe inner hash to rfc mapping
In reply to Parav Pandithyperlinks inside the C comments do not work well.
Until we find out a way to represent it, lets present this in table form.
--- device-types/net/description.tex | 35 ++++++++++++++++++++++---------- 1 file changed, 24 insertions(+), 11 deletions(-)
device-types/net/description.tex +24 -11
@@ -1065,17 +1065,30 @@ \subsubsection{Processing of Incoming Packets}\label{sec:Device Types / Network Hash calculation for incoming packets / Encapsulation types supported/enabled for inner header hash} Encapsulation types applicable for inner header hash: -\begin{lstlisting} -#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_2784 (1 << 0) /* \hyperref[intro:gre_rfc2784]{[GRE_rfc2784]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_2890 (1 << 1) /* \hyperref[intro:gre_rfc2890]{[GRE_rfc2890]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_7676 (1 << 2) /* \hyperref[intro:gre_rfc7676]{[GRE_rfc7676]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_UDP (1 << 3) /* \hyperref[intro:gre_in_udp_rfc8086]{[GRE-in-UDP]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_VXLAN (1 << 4) /* \hyperref[intro:vxlan]{[VXLAN]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_VXLAN_GPE (1 << 5) /* \hyperref[intro:vxlan_gpe]{[VXLAN-GPE]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_GENEVE (1 << 6) /* \hyperref[intro:geneve]{[GENEVE]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_IPIP (1 << 7) /* \hyperref[intro:ipip]{[IPIP]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_NVGRE (1 << 8) /* \hyperref[intro:nvgre]{[NVGRE]} */ -\end{lstlisting} + +\begin{tabular}{|l|l|l|} +\hline +Inner header hash type & Value & Reference \\ +\hline \hline +VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_2784 & (1 << 0) & \hyperref[intro:rfc2784]{RFC2784} \\ +\hline +VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_2890 & (1 << 1) & \hyperref[intro:rfc2784]{RFC2784} \\ +\hline +VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_7676 & (1 << 2) & \hyperref[intro:rfc7676]{RFC7676} \\ +\hline +VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_UDP & (1 << 3) & \hyperref[intro:rfc8086]{GRE in UDP} \\ +\hline +VIRTIO_NET_HASH_TUNNEL_TYPE_VXLAN & (1 << 4) & \hyperref[intro:vxlan]{VXLAN} \\ +\hline +VIRTIO_NET_HASH_TUNNEL_TYPE_VXLAN_GPE & (1 << 5) & \hyperref[intro:vxlan gpe]{VXLAN GPE} \\ +\hline +VIRTIO_NET_HASH_TUNNEL_TYPE_GENEVE & (1 << 6) & \hyperref[intro:geneve]{GENEVE} \\ +\hline +VIRTIO_NET_HASH_TUNNEL_TYPE_IPIP & (1 << 7) & \hyperref[intro:ipip]{IPIP} \\ +\hline +VIRTIO_NET_HASH_TUNNEL_TYPE_NVGRE & (1 << 8) & \hyperref[intro:nvgre]{NVGRE} \\ +\hline +\end{tabular} \subparagraph{Advice} Example uses of the inner header hash:
Signature · 18 lines
2.26.2 This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC. In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting. Subscribe: [email protected] Unsubscribe: [email protected] List help: [email protected] List archive: https://lists.oasis-open.org/archives/virtio-comment/ Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists Committee: https://www.oasis-open.org/committees/virtio/ Join OASIS: https://www.oasis-open.org/join/
[virtio-comment] Re: [PATCH 3/4] virtio-net: Use table to describe inner hash to rfc mapping
Quoted 18 lines · Parav Pandit
hyperlinks inside the C comments do not work well.
Until we find out a way to represent it, lets present this in table form.Signed-off-by Parav Pandit <[email protected]>--- device-types/net/description.tex | 35 ++++++++++++++++++++++---------- 1 file changed, 24 insertions(+), 11 deletions(-)device-types/net/description.tex +0
-1@@ -1065,17 +1065,30 @@ \subsubsection{Processing of Incoming Packets}\label{sec:Device Types / Network Hash calculation for incoming packets / Encapsulation types supported/enabled for inner header hash} Encapsulation types applicable for inner header hash: -\begin{lstlisting}
device-types/net/description.tex \subsubsection{Processing of Incoming Packets}\label{sec:Device Types / Network · line 1078
Quoted 10 lines
device-types/net/description.tex +0
-10-#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_2784 (1 << 0) /* \hyperref[intro:gre_rfc2784]{[GRE_rfc2784]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_2890 (1 << 1) /* \hyperref[intro:gre_rfc2890]{[GRE_rfc2890]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_7676 (1 << 2) /* \hyperref[intro:gre_rfc7676]{[GRE_rfc7676]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_UDP (1 << 3) /* \hyperref[intro:gre_in_udp_rfc8086]{[GRE-in-UDP]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_VXLAN (1 << 4) /* \hyperref[intro:vxlan]{[VXLAN]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_VXLAN_GPE (1 << 5) /* \hyperref[intro:vxlan_gpe]{[VXLAN-GPE]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_GENEVE (1 << 6) /* \hyperref[intro:geneve]{[GENEVE]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_IPIP (1 << 7) /* \hyperref[intro:ipip]{[IPIP]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_NVGRE (1 << 8) /* \hyperref[intro:nvgre]{[NVGRE]} */ -\end{lstlisting}
Hmm. escapechar did not work then?
Quoted 29 lines
device-types/net/description.tex +24
-0+ +\begin{tabular}{|l|l|l|} +\hline +Inner header hash type & Value & Reference \\ +\hline \hline +VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_2784 & (1 << 0) & \hyperref[intro:rfc2784]{RFC2784} \\ +\hline +VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_2890 & (1 << 1) & \hyperref[intro:rfc2784]{RFC2784} \\ +\hline +VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_7676 & (1 << 2) & \hyperref[intro:rfc7676]{RFC7676} \\ +\hline +VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_UDP & (1 << 3) & \hyperref[intro:rfc8086]{GRE in UDP} \\ +\hline +VIRTIO_NET_HASH_TUNNEL_TYPE_VXLAN & (1 << 4) & \hyperref[intro:vxlan]{VXLAN} \\ +\hline +VIRTIO_NET_HASH_TUNNEL_TYPE_VXLAN_GPE & (1 << 5) & \hyperref[intro:vxlan gpe]{VXLAN GPE} \\ +\hline +VIRTIO_NET_HASH_TUNNEL_TYPE_GENEVE & (1 << 6) & \hyperref[intro:geneve]{GENEVE} \\ +\hline +VIRTIO_NET_HASH_TUNNEL_TYPE_IPIP & (1 << 7) & \hyperref[intro:ipip]{IPIP} \\ +\hline +VIRTIO_NET_HASH_TUNNEL_TYPE_NVGRE & (1 << 8) & \hyperref[intro:nvgre]{NVGRE} \\ +\hline +\end{tabular} \subparagraph{Advice} Example uses of the inner header hash:Signature · 1 line
2.26.2
This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting.
Subscribe: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
[virtio-comment] RE: [PATCH 3/4] virtio-net: Use table to describe inner hash to rfc mapping
Quoted 5 lines
From: Michael S. Tsirkin <[email protected]>
Sent: Wednesday, July 12, 2023 6:41 PM
Hmm. escapechar did not work then?
Forgot to mention, I tried it, it didn't work.
Quoted 21 lines
Review
Quoted 12 lines
(quoted diff) +11
-0+ +\begin{tabular}{|l|l|l|} +\hline +Inner header hash type & Value & Reference \\ \hline \hline +VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_2784 & (1 << 0) & +\hyperref[intro:rfc2784]{RFC2784} \\ \hline +VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_2890 & (1 << 1) & +\hyperref[intro:rfc2784]{RFC2784} \\ \hline +VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_7676 & (1 << 2) & +\hyperref[intro:rfc7676]{RFC7676} \\ \hline +VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_UDP & (1 << 3) &\hyperref[intro:rfc8086]{GRE in UDP} \\
Quoted 2 lines
+\hline
+VIRTIO_NET_HASH_TUNNEL_TYPE_VXLAN & (1 << 4) &\hyperref[intro:vxlan]{VXLAN} \\
Review
Quoted 4 lines
+\hline
(quoted diff) +3
-0+VIRTIO_NET_HASH_TUNNEL_TYPE_VXLAN_GPE & (1 << 5) & +\hyperref[intro:vxlan gpe]{VXLAN GPE} \\ \hline +VIRTIO_NET_HASH_TUNNEL_TYPE_GENEVE & (1 << 6) &\hyperref[intro:geneve]{GENEVE} \\
Quoted 13 lines
Quoted 2 lines
+\hline
+VIRTIO_NET_HASH_TUNNEL_TYPE_IPIP & (1 << 7) &\hyperref[intro:ipip]{IPIP} \\
Quoted 2 lines
+\hline
+VIRTIO_NET_HASH_TUNNEL_TYPE_NVGRE & (1 << 8) &\hyperref[intro:nvgre]{NVGRE} \\
Quoted 7 lines
+\hline
+\end{tabular}\subparagraph{Advice}
Example uses of the inner header hash:
--
2.26.2
This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting.
Subscribe: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
[virtio-comment] RE: [PATCH 3/4] virtio-net: Use table to describe inner hash to rfc mapping
Quoted 5 lines · Parav Pandit
Quoted 3 lines
From: Michael S. Tsirkin <[email protected]>
Sent: Wednesday, July 12, 2023 6:41 PM
Hmm. escapechar did not work then?Forgot to mention, I tried it, it didn't work.
It seemed to work for me (at least in the pdf) -- I'd prefer that one as a minimal change.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
[virtio-comment] Re: [PATCH 3/4] virtio-net: Use table to describe inner hash to rfc mapping
Quoted 10 lines · Cornelia Huck
Quoted 5 lines · Parav Pandit
Quoted 3 lines
From: Michael S. Tsirkin <[email protected]>
Sent: Wednesday, July 12, 2023 6:41 PM
Hmm. escapechar did not work then?Forgot to mention, I tried it, it didn't work.
It seemed to work for me (at least in the pdf) -- I'd prefer that one as a minimal change.
Yes it really should. Could you post yours please?
This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting.
Subscribe: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
PATCH 4/4 virtio-net: Use note instead of advice
In reply to Parav PanditSection like "Advice" is not the current practice. Lets capture such advice as notes.
--- device-types/net/description.tex | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
device-types/net/description.tex +3 -1
@@ -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
Signature · 18 lines
2.26.2 This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC. In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting. Subscribe: [email protected] Unsubscribe: [email protected] List help: [email protected] List archive: https://lists.oasis-open.org/archives/virtio-comment/ Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists Committee: https://www.oasis-open.org/committees/virtio/ Join OASIS: https://www.oasis-open.org/join/
Quoted 23 lines · Parav Pandit
This short patches fixes the editing errors that stops the pdf and html generation.
These 3 fixes are for the patch [1] for the github issue [2].
[1] https://lists.oasis-open.org/archives/virtio-comment/202307/msg00024.html
[2] https://github.com/oasis-tcs/virtio-spec/issues/173Patch summary:
patch-1 place C code under listing
patch-2 avoid hyphen and extra braces
patch-3 use table as hyperlink do not work well in C code listing patch-4 refer 'advice' as 'note'Patch 1 to 3 appears to be must in the testing.
Patch 4 is not a fix and can be done later if it requires discussion.Parav Pandit (4):
virtio-net: Place C code under listing
virtio-net: Avoid hyphen and extra braces
virtio-net: Use table to describe inner hash to rfc mapping
virtio-net: Use note instead of advice
Quoted 4 lines
device-types/net/description.tex | 45 ++++++++++++++++++++++---------- introduction.tex | 15 +++++------ 2 files changed, 38 insertions(+), 22 deletions(-)
FTR, this is the diff I have locally (I had missed one underscore in the references yesterday...); maybe we can make the intra-reference links in introdcution.tex a bit nicer, but otherwise, this should be the minimal change to make this build:
device-types/net/description.tex +12 -10
@@ -1024,12 +1024,14 @@ \subsubsection{Processing of Incoming Packets}\label{sec:Device Types / Network If VIRTIO_NET_F_HASH_TUNNEL has been negotiated, the driver can send the command VIRTIO_NET_CTRL_HASH_TUNNEL_SET to configure the calculation of the inner header hash. +\begin{lstlisting} struct virtnet_hash_tunnel { le32 enabled_tunnel_types; }; #define VIRTIO_NET_CTRL_HASH_TUNNEL 7 #define VIRTIO_NET_CTRL_HASH_TUNNEL_SET 0 +\end{lstlisting} Field \field{enabled_tunnel_types} contains the bitmask of encapsulation types enabled for inner header hash. See \ref{sec:Device Types / Network Device / Device Operation / Processing of Incoming Packets /
@@ -1063,16 +1065,16 @@ \subsubsection{Processing of Incoming Packets}\label{sec:Device Types / Network Hash calculation for incoming packets / Encapsulation types supported/enabled for inner header hash} Encapsulation types applicable for inner header hash: -\begin{lstlisting} -#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_2784 (1 << 0) /* \hyperref[intro:gre_rfc2784]{[GRE_rfc2784]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_2890 (1 << 1) /* \hyperref[intro:gre_rfc2890]{[GRE_rfc2890]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_7676 (1 << 2) /* \hyperref[intro:gre_rfc7676]{[GRE_rfc7676]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_UDP (1 << 3) /* \hyperref[intro:gre_in_udp_rfc8086]{[GRE-in-UDP]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_VXLAN (1 << 4) /* \hyperref[intro:vxlan]{[VXLAN]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_VXLAN_GPE (1 << 5) /* \hyperref[intro:vxlan_gpe]{[VXLAN-GPE]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_GENEVE (1 << 6) /* \hyperref[intro:geneve]{[GENEVE]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_IPIP (1 << 7) /* \hyperref[intro:ipip]{[IPIP]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_NVGRE (1 << 8) /* \hyperref[intro:nvgre]{[NVGRE]} */ +\begin{lstlisting}[escapechar=|] +#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_2784 (1 << 0) /* |\hyperref[intro:rfc2784]{[RFC2784]}| */ +#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_2890 (1 << 1) /* |\hyperref[intro:rfc2890]{[RFC2890]}| */ +#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_7676 (1 << 2) /* |\hyperref[intro:rfc7676]{[RFC7676]}| */ +#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_UDP (1 << 3) /* |\hyperref[intro:rfc8086]{[GRE-in-UDP]}| */ +#define VIRTIO_NET_HASH_TUNNEL_TYPE_VXLAN (1 << 4) /* |\hyperref[intro:vxlan]{[VXLAN]}| */ +#define VIRTIO_NET_HASH_TUNNEL_TYPE_VXLAN_GPE (1 << 5) /* |\hyperref[intro:vxlan-gpe]{[VXLAN-GPE]}| */ +#define VIRTIO_NET_HASH_TUNNEL_TYPE_GENEVE (1 << 6) /* |\hyperref[intro:geneve]{[GENEVE]}| */ +#define VIRTIO_NET_HASH_TUNNEL_TYPE_IPIP (1 << 7) /* |\hyperref[intro:ipip]{[IPIP]}| */ +#define VIRTIO_NET_HASH_TUNNEL_TYPE_NVGRE (1 << 8) /* |\hyperref[intro:nvgre]{[NVGRE]}| */ \end{lstlisting} \subparagraph{Advice}
introduction.tex +6 -6
@@ -102,18 +102,18 @@ \section{Normative References}\label{sec:Normative References} Standards for Efficient Cryptography Group(SECG), ``SEC1: Elliptic Cureve Cryptography'', Version 1.0, September 2000. \newline\url{https://www.secg.org/sec1-v2.pdf}\\ - \phantomsection\label{intro:gre_rfc2784}\textbf{[GRE_rfc2784]} & + \phantomsection\label{intro:rfc2784}\textbf{[RFC2784]} & Generic Routing Encapsulation. This protocol is only specified for IPv4 and used as either the payload or delivery protocol. \newline\url{https://datatracker.ietf.org/doc/rfc2784/}\\ - \phantomsection\label{intro:gre_rfc2890}\textbf{[GRE_rfc2890]} & - Key and Sequence Number Extensions to GRE \ref{intro:gre_rfc2784}. This protocol describes extensions by which two fields, Key and - Sequence Number, can be optionally carried in the GRE Header \ref{intro:gre_rfc2784}. + \phantomsection\label{intro:rfc2890}\textbf{[RFC2890]} & + Key and Sequence Number Extensions to GRE \ref{intro:rfc2784}. This protocol describes extensions by which two fields, Key and + Sequence Number, can be optionally carried in the GRE Header \ref{intro:rfc2784}. \newline\url{https://www.rfc-editor.org/rfc/rfc2890}\\ - \phantomsection\label{intro:gre_rfc7676}\textbf{[GRE_rfc7676]} & + \phantomsection\label{intro:rfc7676}\textbf{[RFC7676]} & IPv6 Support for Generic Routing Encapsulation (GRE). This protocol is specified for IPv6 and used as either the payload or delivery protocol. Note that this does not change the GRE header format or any behaviors specified by RFC 2784 or RFC 2890. \newline\url{https://datatracker.ietf.org/doc/rfc7676/}\\ - \phantomsection\label{intro:gre_in_udp_rfc8086}\textbf{[GRE-in-UDP]} & + \phantomsection\label{intro:rfc8086}\textbf{[GRE-in-UDP]} & GRE-in-UDP Encapsulation. This specifies a method of encapsulating network protocol packets within GRE and UDP headers. This protocol is specified for IPv4 and IPv6, and used as either the payload or delivery protocol. \newline\url{https://www.rfc-editor.org/rfc/rfc8086}\\
This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting.
Subscribe: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
Quoted 30 lines · Cornelia Huck
Quoted 23 lines · Parav Pandit
This short patches fixes the editing errors that stops the pdf and html generation.
These 3 fixes are for the patch [1] for the github issue [2].
[1] https://lists.oasis-open.org/archives/virtio-comment/202307/msg00024.html
[2] https://github.com/oasis-tcs/virtio-spec/issues/173Patch summary:
patch-1 place C code under listing
patch-2 avoid hyphen and extra braces
patch-3 use table as hyperlink do not work well in C code listing patch-4 refer 'advice' as 'note'Patch 1 to 3 appears to be must in the testing.
Patch 4 is not a fix and can be done later if it requires discussion.Parav Pandit (4):
virtio-net: Place C code under listing
virtio-net: Avoid hyphen and extra braces
virtio-net: Use table to describe inner hash to rfc mapping
virtio-net: Use note instead of adviceQuoted 4 lines
device-types/net/description.tex | 45 ++++++++++++++++++++++---------- introduction.tex | 15 +++++------ 2 files changed, 38 insertions(+), 22 deletions(-)
Quoted 4 lines
FTR, this is the diff I have locally (I had missed one underscore in the references yesterday...); maybe we can make the intra-reference links in introdcution.tex a bit nicer, but otherwise, this should be the minimal change to make this build:
For the "make it look nicer" part, I think this one would get the job done; opinions?
introduction.tex +2 -2
@@ -106,8 +106,8 @@ \section{Normative References}\label{sec:Normative References} Generic Routing Encapsulation. This protocol is only specified for IPv4 and used as either the payload or delivery protocol. \newline\url{https://datatracker.ietf.org/doc/rfc2784/}\\ \phantomsection\label{intro:rfc2890}\textbf{[RFC2890]} & - Key and Sequence Number Extensions to GRE \ref{intro:rfc2784}. This protocol describes extensions by which two fields, Key and - Sequence Number, can be optionally carried in the GRE Header \ref{intro:rfc2784}. + Key and Sequence Number Extensions to \hyperref[intro:rfc2784]{GRE}. This protocol describes extensions by which two fields, Key and + Sequence Number, can be optionally carried in the \hyperref[intro:rfc2784]{GRE} Header. \newline\url{https://www.rfc-editor.org/rfc/rfc2890}\\ \phantomsection\label{intro:rfc7676}\textbf{[RFC7676]} & IPv6 Support for Generic Routing Encapsulation (GRE). This protocol is specified for IPv6 and used as either the payload or
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
Quoted 45 lines · Cornelia Huck
Quoted 30 lines · Cornelia Huck
Quoted 23 lines · Parav Pandit
This short patches fixes the editing errors that stops the pdf and html generation.
These 3 fixes are for the patch [1] for the github issue [2].
[1] https://lists.oasis-open.org/archives/virtio-comment/202307/msg00024.html
[2] https://github.com/oasis-tcs/virtio-spec/issues/173Patch summary:
patch-1 place C code under listing
patch-2 avoid hyphen and extra braces
patch-3 use table as hyperlink do not work well in C code listing patch-4 refer 'advice' as 'note'Patch 1 to 3 appears to be must in the testing.
Patch 4 is not a fix and can be done later if it requires discussion.Parav Pandit (4):
virtio-net: Place C code under listing
virtio-net: Avoid hyphen and extra braces
virtio-net: Use table to describe inner hash to rfc mapping
virtio-net: Use note instead of adviceQuoted 4 lines
device-types/net/description.tex | 45 ++++++++++++++++++++++---------- introduction.tex | 15 +++++------ 2 files changed, 38 insertions(+), 22 deletions(-)Quoted 4 lines
FTR, this is the diff I have locally (I had missed one underscore in the references yesterday...); maybe we can make the intra-reference links in introdcution.tex a bit nicer, but otherwise, this should be the minimal change to make this build:
For the "make it look nicer" part, I think this one would get the job done; opinions?
introduction.tex +0
-0
introduction.tex \section{Normative References}\label{sec:Normative References} · line 110
Quoted 7 lines
introduction.tex +2
-2@@ -106,8 +106,8 @@ \section{Normative References}\label{sec:Normative References} Generic Routing Encapsulation. This protocol is only specified for IPv4 and used as either the payload or delivery protocol. \newline\url{https://datatracker.ietf.org/doc/rfc2784/}\\ \phantomsection\label{intro:rfc2890}\textbf{[RFC2890]} & - Key and Sequence Number Extensions to GRE \ref{intro:rfc2784}. This protocol describes extensions by which two fields, Key and - Sequence Number, can be optionally carried in the GRE Header \ref{intro:rfc2784}. + Key and Sequence Number Extensions to \hyperref[intro:rfc2784]{GRE}. This protocol describes extensions by which two fields, Key and + Sequence Number, can be optionally carried in the \hyperref[intro:rfc2784]{GRE} Header.
This does look nicer.
introduction.tex \section{Normative References}\label{sec:Normative References} · line 113
Quoted 3 lines
introduction.tex +0
-0\newline\url{https://www.rfc-editor.org/rfc/rfc2890}\\ \phantomsection\label{intro:rfc7676}\textbf{[RFC7676]} & IPv6 Support for Generic Routing Encapsulation (GRE). This protocol is specified for IPv6 and used as either the payload or
This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting.
Subscribe: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
Quoted 30 lines · Cornelia Huck
Quoted 23 lines · Parav Pandit
This short patches fixes the editing errors that stops the pdf and html generation.
These 3 fixes are for the patch [1] for the github issue [2].
[1] https://lists.oasis-open.org/archives/virtio-comment/202307/msg00024.html
[2] https://github.com/oasis-tcs/virtio-spec/issues/173Patch summary:
patch-1 place C code under listing
patch-2 avoid hyphen and extra braces
patch-3 use table as hyperlink do not work well in C code listing patch-4 refer 'advice' as 'note'Patch 1 to 3 appears to be must in the testing.
Patch 4 is not a fix and can be done later if it requires discussion.Parav Pandit (4):
virtio-net: Place C code under listing
virtio-net: Avoid hyphen and extra braces
virtio-net: Use table to describe inner hash to rfc mapping
virtio-net: Use note instead of adviceQuoted 4 lines
device-types/net/description.tex | 45 ++++++++++++++++++++++---------- introduction.tex | 15 +++++------ 2 files changed, 38 insertions(+), 22 deletions(-)
Quoted 4 lines
FTR, this is the diff I have locally (I had missed one underscore in the references yesterday...); maybe we can make the intra-reference links in introdcution.tex a bit nicer, but otherwise, this should be the minimal change to make this build:
Perfect. Seems like clearly an editorial fix.
Heng Qi, in the future I'd like to ask you to please build the spec and review the resulting PDF and HTML, before posting.
Quoted 65 lines
device-types/net/description.tex +12
-10@@ -1024,12 +1024,14 @@ \subsubsection{Processing of Incoming Packets}\label{sec:Device Types / Network If VIRTIO_NET_F_HASH_TUNNEL has been negotiated, the driver can send the command VIRTIO_NET_CTRL_HASH_TUNNEL_SET to configure the calculation of the inner header hash. +\begin{lstlisting} struct virtnet_hash_tunnel { le32 enabled_tunnel_types; }; #define VIRTIO_NET_CTRL_HASH_TUNNEL 7 #define VIRTIO_NET_CTRL_HASH_TUNNEL_SET 0 +\end{lstlisting} Field \field{enabled_tunnel_types} contains the bitmask of encapsulation types enabled for inner header hash. See \ref{sec:Device Types / Network Device / Device Operation / Processing of Incoming Packets /@@ -1063,16 +1065,16 @@ \subsubsection{Processing of Incoming Packets}\label{sec:Device Types / Network Hash calculation for incoming packets / Encapsulation types supported/enabled for inner header hash} Encapsulation types applicable for inner header hash: -\begin{lstlisting} -#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_2784 (1 << 0) /* \hyperref[intro:gre_rfc2784]{[GRE_rfc2784]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_2890 (1 << 1) /* \hyperref[intro:gre_rfc2890]{[GRE_rfc2890]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_7676 (1 << 2) /* \hyperref[intro:gre_rfc7676]{[GRE_rfc7676]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_UDP (1 << 3) /* \hyperref[intro:gre_in_udp_rfc8086]{[GRE-in-UDP]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_VXLAN (1 << 4) /* \hyperref[intro:vxlan]{[VXLAN]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_VXLAN_GPE (1 << 5) /* \hyperref[intro:vxlan_gpe]{[VXLAN-GPE]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_GENEVE (1 << 6) /* \hyperref[intro:geneve]{[GENEVE]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_IPIP (1 << 7) /* \hyperref[intro:ipip]{[IPIP]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_NVGRE (1 << 8) /* \hyperref[intro:nvgre]{[NVGRE]} */ +\begin{lstlisting}[escapechar=|] +#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_2784 (1 << 0) /* |\hyperref[intro:rfc2784]{[RFC2784]}| */ +#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_2890 (1 << 1) /* |\hyperref[intro:rfc2890]{[RFC2890]}| */ +#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_7676 (1 << 2) /* |\hyperref[intro:rfc7676]{[RFC7676]}| */ +#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_UDP (1 << 3) /* |\hyperref[intro:rfc8086]{[GRE-in-UDP]}| */ +#define VIRTIO_NET_HASH_TUNNEL_TYPE_VXLAN (1 << 4) /* |\hyperref[intro:vxlan]{[VXLAN]}| */ +#define VIRTIO_NET_HASH_TUNNEL_TYPE_VXLAN_GPE (1 << 5) /* |\hyperref[intro:vxlan-gpe]{[VXLAN-GPE]}| */ +#define VIRTIO_NET_HASH_TUNNEL_TYPE_GENEVE (1 << 6) /* |\hyperref[intro:geneve]{[GENEVE]}| */ +#define VIRTIO_NET_HASH_TUNNEL_TYPE_IPIP (1 << 7) /* |\hyperref[intro:ipip]{[IPIP]}| */ +#define VIRTIO_NET_HASH_TUNNEL_TYPE_NVGRE (1 << 8) /* |\hyperref[intro:nvgre]{[NVGRE]}| */ \end{lstlisting} \subparagraph{Advice}introduction.tex +4
-4@@ -102,18 +102,18 @@ \section{Normative References}\label{sec:Normative References} Standards for Efficient Cryptography Group(SECG), ``SEC1: Elliptic Cureve Cryptography'', Version 1.0, September 2000. \newline\url{https://www.secg.org/sec1-v2.pdf}\\ - \phantomsection\label{intro:gre_rfc2784}\textbf{[GRE_rfc2784]} & + \phantomsection\label{intro:rfc2784}\textbf{[RFC2784]} & Generic Routing Encapsulation. This protocol is only specified for IPv4 and used as either the payload or delivery protocol. \newline\url{https://datatracker.ietf.org/doc/rfc2784/}\\ - \phantomsection\label{intro:gre_rfc2890}\textbf{[GRE_rfc2890]} & - Key and Sequence Number Extensions to GRE \ref{intro:gre_rfc2784}. This protocol describes extensions by which two fields, Key and - Sequence Number, can be optionally carried in the GRE Header \ref{intro:gre_rfc2784}. + \phantomsection\label{intro:rfc2890}\textbf{[RFC2890]} & + Key and Sequence Number Extensions to GRE \ref{intro:rfc2784}. This protocol describes extensions by which two fields, Key and + Sequence Number, can be optionally carried in the GRE Header \ref{intro:rfc2784}. \newline\url{https://www.rfc-editor.org/rfc/rfc2890}\\
introduction.tex \section{Normative References}\label{sec:Normative References} · line 119
Quoted 10 lines
introduction.tex +2
-2- \phantomsection\label{intro:gre_rfc7676}\textbf{[GRE_rfc7676]} & + \phantomsection\label{intro:rfc7676}\textbf{[RFC7676]} & IPv6 Support for Generic Routing Encapsulation (GRE). This protocol is specified for IPv6 and used as either the payload or delivery protocol. Note that this does not change the GRE header format or any behaviors specified by RFC 2784 or RFC 2890. \newline\url{https://datatracker.ietf.org/doc/rfc7676/}\\ - \phantomsection\label{intro:gre_in_udp_rfc8086}\textbf{[GRE-in-UDP]} & + \phantomsection\label{intro:rfc8086}\textbf{[GRE-in-UDP]} & GRE-in-UDP Encapsulation. This specifies a method of encapsulating network protocol packets within GRE and UDP headers. This protocol is specified for IPv4 and IPv6, and used as either the payload or delivery protocol. \newline\url{https://www.rfc-editor.org/rfc/rfc8086}\\
This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting.
Subscribe: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
Quoted 30 lines · Michael S. Tsirkin
Quoted 29 lines · Cornelia Huck
Quoted 27 lines · Parav Pandit
This short patches fixes the editing errors that stops the pdf and html generation.
These 3 fixes are for the patch [1] for the github issue [2].
[1] https://lists.oasis-open.org/archives/virtio-comment/202307/msg00024.html
[2] https://github.com/oasis-tcs/virtio-spec/issues/173Patch summary:
patch-1 place C code under listing
patch-2 avoid hyphen and extra braces
patch-3 use table as hyperlink do not work well in C code listing patch-4 refer 'advice' as 'note'Patch 1 to 3 appears to be must in the testing.
Patch 4 is not a fix and can be done later if it requires discussion.Parav Pandit (4):
virtio-net: Place C code under listing
virtio-net: Avoid hyphen and extra braces
virtio-net: Use table to describe inner hash to rfc mapping
virtio-net: Use note instead of advicedevice-types/net/description.tex | 45 ++++++++++++++++++++++---------- introduction.tex | 15 +++++------ 2 files changed, 38 insertions(+), 22 deletions(-)
Quoted 8 lines
Quoted 4 lines
FTR, this is the diff I have locally (I had missed one underscore in the references yesterday...); maybe we can make the intra-reference links in introdcution.tex a bit nicer, but otherwise, this should be the minimal change to make this build:
Perfect. Seems like clearly an editorial fix.
Heng Qi, in the future I'd like to ask you to please build the spec and review the resulting PDF and HTML, before posting.
Yes, I will!
Quoted 70 lines
Quoted 70 lines
device-types/net/description.tex +12
-10@@ -1024,12 +1024,14 @@ \subsubsection{Processing of Incoming Packets}\label{sec:Device Types / Network If VIRTIO_NET_F_HASH_TUNNEL has been negotiated, the driver can send the command VIRTIO_NET_CTRL_HASH_TUNNEL_SET to configure the calculation of the inner header hash. +\begin{lstlisting} struct virtnet_hash_tunnel { le32 enabled_tunnel_types; }; #define VIRTIO_NET_CTRL_HASH_TUNNEL 7 #define VIRTIO_NET_CTRL_HASH_TUNNEL_SET 0 +\end{lstlisting} Field \field{enabled_tunnel_types} contains the bitmask of encapsulation types enabled for inner header hash. See \ref{sec:Device Types / Network Device / Device Operation / Processing of Incoming Packets /@@ -1063,16 +1065,16 @@ \subsubsection{Processing of Incoming Packets}\label{sec:Device Types / Network Hash calculation for incoming packets / Encapsulation types supported/enabled for inner header hash} Encapsulation types applicable for inner header hash: -\begin{lstlisting} -#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_2784 (1 << 0) /* \hyperref[intro:gre_rfc2784]{[GRE_rfc2784]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_2890 (1 << 1) /* \hyperref[intro:gre_rfc2890]{[GRE_rfc2890]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_7676 (1 << 2) /* \hyperref[intro:gre_rfc7676]{[GRE_rfc7676]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_UDP (1 << 3) /* \hyperref[intro:gre_in_udp_rfc8086]{[GRE-in-UDP]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_VXLAN (1 << 4) /* \hyperref[intro:vxlan]{[VXLAN]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_VXLAN_GPE (1 << 5) /* \hyperref[intro:vxlan_gpe]{[VXLAN-GPE]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_GENEVE (1 << 6) /* \hyperref[intro:geneve]{[GENEVE]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_IPIP (1 << 7) /* \hyperref[intro:ipip]{[IPIP]} */ -#define VIRTIO_NET_HASH_TUNNEL_TYPE_NVGRE (1 << 8) /* \hyperref[intro:nvgre]{[NVGRE]} */ +\begin{lstlisting}[escapechar=|] +#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_2784 (1 << 0) /* |\hyperref[intro:rfc2784]{[RFC2784]}| */ +#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_2890 (1 << 1) /* |\hyperref[intro:rfc2890]{[RFC2890]}| */ +#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_7676 (1 << 2) /* |\hyperref[intro:rfc7676]{[RFC7676]}| */ +#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_UDP (1 << 3) /* |\hyperref[intro:rfc8086]{[GRE-in-UDP]}| */ +#define VIRTIO_NET_HASH_TUNNEL_TYPE_VXLAN (1 << 4) /* |\hyperref[intro:vxlan]{[VXLAN]}| */ +#define VIRTIO_NET_HASH_TUNNEL_TYPE_VXLAN_GPE (1 << 5) /* |\hyperref[intro:vxlan-gpe]{[VXLAN-GPE]}| */ +#define VIRTIO_NET_HASH_TUNNEL_TYPE_GENEVE (1 << 6) /* |\hyperref[intro:geneve]{[GENEVE]}| */ +#define VIRTIO_NET_HASH_TUNNEL_TYPE_IPIP (1 << 7) /* |\hyperref[intro:ipip]{[IPIP]}| */ +#define VIRTIO_NET_HASH_TUNNEL_TYPE_NVGRE (1 << 8) /* |\hyperref[intro:nvgre]{[NVGRE]}| */ \end{lstlisting} \subparagraph{Advice}introduction.tex +5
-5@@ -102,18 +102,18 @@ \section{Normative References}\label{sec:Normative References} Standards for Efficient Cryptography Group(SECG), ``SEC1: Elliptic Cureve Cryptography'', Version 1.0, September 2000. \newline\url{https://www.secg.org/sec1-v2.pdf}\\ - \phantomsection\label{intro:gre_rfc2784}\textbf{[GRE_rfc2784]} & + \phantomsection\label{intro:rfc2784}\textbf{[RFC2784]} & Generic Routing Encapsulation. This protocol is only specified for IPv4 and used as either the payload or delivery protocol. \newline\url{https://datatracker.ietf.org/doc/rfc2784/}\\ - \phantomsection\label{intro:gre_rfc2890}\textbf{[GRE_rfc2890]} & - Key and Sequence Number Extensions to GRE \ref{intro:gre_rfc2784}. This protocol describes extensions by which two fields, Key and - Sequence Number, can be optionally carried in the GRE Header \ref{intro:gre_rfc2784}. + \phantomsection\label{intro:rfc2890}\textbf{[RFC2890]} & + Key and Sequence Number Extensions to GRE \ref{intro:rfc2784}. This protocol describes extensions by which two fields, Key and + Sequence Number, can be optionally carried in the GRE Header \ref{intro:rfc2784}. \newline\url{https://www.rfc-editor.org/rfc/rfc2890}\\ - \phantomsection\label{intro:gre_rfc7676}\textbf{[GRE_rfc7676]} & + \phantomsection\label{intro:rfc7676}\textbf{[RFC7676]} &
Quoted 8 lines
introduction.tex \section{Normative References}\label{sec:Normative References} · line 119
Quoted 8 lines
introduction.tex +1
-1IPv6 Support for Generic Routing Encapsulation (GRE). This protocol is specified for IPv6 and used as either the payload or delivery protocol. Note that this does not change the GRE header format or any behaviors specified by RFC 2784 or RFC 2890. \newline\url{https://datatracker.ietf.org/doc/rfc7676/}\\ - \phantomsection\label{intro:gre_in_udp_rfc8086}\textbf{[GRE-in-UDP]} & + \phantomsection\label{intro:rfc8086}\textbf{[GRE-in-UDP]} & GRE-in-UDP Encapsulation. This specifies a method of encapsulating network protocol packets within GRE and UDP headers. This protocol is specified for IPv4 and IPv6, and used as either the payload or delivery protocol. \newline\url{https://www.rfc-editor.org/rfc/rfc8086}\\
This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting.
Subscribe: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/