From: "Michael S. Tsirkin" <mst@redhat.com>
To: virtio-comment@lists.oasis-open.org
Cc: Yuri Benditovich <yuri.benditovich@daynix.com>
Subject: [virtio-comment] [PATCH] virtio-net/rss: maximal -> maximum
Date: Sun, 1 Mar 2020 03:55:18 -0500 [thread overview]
Message-ID: <20200301085437.804801-1-mst@redhat.com> (raw)
Maximal can mean "local as opposed to a global maximum". Rest of the
spec says maximum everywhere. Let's be consistent.
Cc: Yuri Benditovich <yuri.benditovich@daynix.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
Going to apply this under the minor cleanups rule.
content.tex | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content.tex b/content.tex
index b91a132..91735e3 100644
--- a/content.tex
+++ b/content.tex
@@ -2999,9 +2999,9 @@ \subsection{Device configuration layout}\label{sec:Device Types / Network Device
Three following fields, \field{rss_max_key_size}, \field{rss_max_indirection_table_length}
and \field{supported_hash_types} only exist if VIRTIO_NET_F_RSS is set.
-Field \field{rss_max_key_size} specifies the maximal supported length of RSS key in bytes.
+Field \field{rss_max_key_size} specifies the maximum supported length of RSS key in bytes.
-Field \field{rss_max_indirection_table_length} specifies the maximal number of 16-bit entries in RSS indirection table.
+Field \field{rss_max_indirection_table_length} specifies the maximum number of 16-bit entries in RSS indirection table.
Field \field{supported_hash_types} contains the bitmask of supported RSS hash types.
--
MST
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/
next reply other threads:[~2020-03-01 8:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-01 8:55 Michael S. Tsirkin [this message]
2020-03-03 8:01 ` [virtio-comment] [PATCH] virtio-net/rss: maximal -> maximum Stefan Hajnoczi
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=20200301085437.804801-1-mst@redhat.com \
--to=mst@redhat.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=yuri.benditovich@daynix.com \
/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