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 4/4] virtio-net: Use note instead of advice
Date: Thu, 13 Jul 2023 01:24:05 +0300 [thread overview]
Message-ID: <20230712222405.455201-5-parav@nvidia.com> (raw)
In-Reply-To: <20230712222405.455201-1-parav@nvidia.com>
Section like "Advice" is not the current practice. Lets capture such
advice as notes.
Signed-off-by: Parav Pandit <parav@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-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: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 22:24 [virtio-dev] [PATCH 0/4] Short document fixes to inner hash feature Parav Pandit
2023-07-12 22:24 ` [virtio-dev] [PATCH 1/4] virtio-net: Place C code under listing Parav Pandit
2023-07-13 9:13 ` [virtio-dev] Re: [virtio-comment] " Cornelia Huck
2023-07-13 11:44 ` [virtio-dev] " Parav Pandit
2023-07-12 22:24 ` [virtio-dev] [PATCH 2/4] virtio-net: Avoid hyphen and extra braces Parav Pandit
2023-07-13 9:16 ` [virtio-dev] " Cornelia Huck
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-dev] " Michael S. Tsirkin
2023-07-12 22:42 ` [virtio-dev] " Parav Pandit
2023-07-13 8:09 ` Cornelia Huck
2023-07-13 11:01 ` [virtio-dev] " Michael S. Tsirkin
2023-07-12 22:24 ` Parav Pandit [this message]
2023-07-13 9:12 ` [virtio-dev] Re: [PATCH 0/4] Short document fixes to inner hash feature Cornelia Huck
2023-07-13 9:32 ` [virtio-dev] Re: [virtio-comment] " Cornelia Huck
2023-07-13 11:00 ` Michael S. Tsirkin
2023-07-13 11:33 ` [virtio-dev] " Michael S. Tsirkin
2023-07-13 11:58 ` 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-5-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).