From: Parav Pandit <parav@nvidia.com>
To: <virtio-comment@lists.oasis-open.org>, <mst@redhat.com>,
<cohuck@redhat.com>
Cc: <virtio-dev@lists.oasis-open.org>, <hengqi@linux.alibaba.com>,
<shahafs@nvidia.com>, Parav Pandit <parav@nvidia.com>
Subject: [virtio-comment] [PATCH 3/4] virtio-net: Use table to describe inner hash to rfc mapping
Date: Thu, 13 Jul 2023 01:24:04 +0300 [thread overview]
Message-ID: <20230712222405.455201-4-parav@nvidia.com> (raw)
In-Reply-To: <20230712222405.455201-1-parav@nvidia.com>
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 <parav@nvidia.com>
---
device-types/net/description.tex | 35 ++++++++++++++++++++++----------
1 file changed, 24 insertions(+), 11 deletions(-)
diff --git a/device-types/net/description.tex b/device-types/net/description.tex
index 53c811f..68311ab 100644
--- a/device-types/net/description.tex
+++ b/device-types/net/description.tex
@@ -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:
--
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: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
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/
WARNING: multiple messages have this Message-ID (diff)
From: Parav Pandit <parav@nvidia.com>
To: <virtio-comment@lists.oasis-open.org>, <mst@redhat.com>,
<cohuck@redhat.com>
Cc: <virtio-dev@lists.oasis-open.org>, <hengqi@linux.alibaba.com>,
<shahafs@nvidia.com>, Parav Pandit <parav@nvidia.com>
Subject: [virtio-dev] [PATCH 3/4] virtio-net: Use table to describe inner hash to rfc mapping
Date: Thu, 13 Jul 2023 01:24:04 +0300 [thread overview]
Message-ID: <20230712222405.455201-4-parav@nvidia.com> (raw)
In-Reply-To: <20230712222405.455201-1-parav@nvidia.com>
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 <parav@nvidia.com>
---
device-types/net/description.tex | 35 ++++++++++++++++++++++----------
1 file changed, 24 insertions(+), 11 deletions(-)
diff --git a/device-types/net/description.tex b/device-types/net/description.tex
index 53c811f..68311ab 100644
--- a/device-types/net/description.tex
+++ b/device-types/net/description.tex
@@ -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:
--
2.26.2
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2023-07-12 22:25 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 22:24 [virtio-comment] [PATCH 0/4] Short document fixes to inner hash feature Parav Pandit
2023-07-12 22:24 ` [virtio-dev] " Parav Pandit
2023-07-12 22:24 ` [virtio-comment] [PATCH 1/4] virtio-net: Place C code under listing Parav Pandit
2023-07-12 22:24 ` [virtio-dev] " Parav Pandit
2023-07-13 9:13 ` [virtio-comment] " Cornelia Huck
2023-07-13 9:13 ` [virtio-dev] " Cornelia Huck
2023-07-13 11:44 ` Parav Pandit
2023-07-13 11:44 ` [virtio-dev] " Parav Pandit
2023-07-12 22:24 ` [virtio-comment] [PATCH 2/4] virtio-net: Avoid hyphen and extra braces Parav Pandit
2023-07-12 22:24 ` [virtio-dev] " Parav Pandit
2023-07-13 9:16 ` [virtio-comment] " Cornelia Huck
2023-07-13 9:16 ` [virtio-dev] " Cornelia Huck
2023-07-12 22:24 ` Parav Pandit [this message]
2023-07-12 22:24 ` [virtio-dev] [PATCH 3/4] virtio-net: Use table to describe inner hash to rfc mapping Parav Pandit
2023-07-12 22:41 ` [virtio-comment] " Michael S. Tsirkin
2023-07-12 22:41 ` [virtio-dev] " Michael S. Tsirkin
2023-07-12 22:42 ` [virtio-comment] " Parav Pandit
2023-07-12 22:42 ` [virtio-dev] " Parav Pandit
2023-07-13 8:09 ` [virtio-comment] " Cornelia Huck
2023-07-13 8:09 ` [virtio-dev] " Cornelia Huck
2023-07-13 11:01 ` [virtio-comment] " Michael S. Tsirkin
2023-07-13 11:01 ` [virtio-dev] " Michael S. Tsirkin
2023-07-12 22:24 ` [virtio-comment] [PATCH 4/4] virtio-net: Use note instead of advice Parav Pandit
2023-07-12 22:24 ` [virtio-dev] " Parav Pandit
2023-07-13 9:12 ` [virtio-comment] Re: [PATCH 0/4] Short document fixes to inner hash feature Cornelia Huck
2023-07-13 9:12 ` [virtio-dev] " Cornelia Huck
2023-07-13 9:32 ` [virtio-comment] " Cornelia Huck
2023-07-13 9:32 ` [virtio-dev] " Cornelia Huck
2023-07-13 11:00 ` Michael S. Tsirkin
2023-07-13 11:00 ` [virtio-dev] " Michael S. Tsirkin
2023-07-13 11:33 ` Michael S. Tsirkin
2023-07-13 11:33 ` [virtio-dev] " Michael S. Tsirkin
2023-07-13 11:58 ` [virtio-comment] " Heng Qi
2023-07-13 11:58 ` [virtio-dev] " Heng Qi
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=20230712222405.455201-4-parav@nvidia.com \
--to=parav@nvidia.com \
--cc=cohuck@redhat.com \
--cc=hengqi@linux.alibaba.com \
--cc=mst@redhat.com \
--cc=shahafs@nvidia.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.