From: Parav Pandit <parav@nvidia.com>
To: <virtio-comment@lists.linux.dev>, <mst@redhat.com>,
<cohuck@redhat.com>, <mvaralar@redhat.com>
Cc: <shahafs@nvidia.com>, Parav Pandit <parav@nvidia.com>
Subject: [PATCH] virtio-net: Rename selectors_limit to classifiers_limit
Date: Sat, 15 Feb 2025 08:06:33 +0200 [thread overview]
Message-ID: <20250215060633.20997-1-parav@nvidia.com> (raw)
A classifier object consists of one or more selectors. The number of
selectors per classifier object is already annotated in the field
selectors_per_classifier_limit.
The field selectors_limit is intended to reflect the limit of
classifier objects. Hence, rename it to classifiers_limit.
Fixes: https://github.com/oasis-tcs/virtio-spec/issues/215
Fixes: 3b7b7371dbed ("virtio-net: Add flow filter device and driver requirements")
Fixes: 899bb0ca24d8 ("virtio-net: Add flow filter capability")
Signed-off-by: Parav Pandit <parav@nvidia.com>
---
device-types/net/description.tex | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/device-types/net/description.tex b/device-types/net/description.tex
index b546cd7..3894c7a 100644
--- a/device-types/net/description.tex
+++ b/device-types/net/description.tex
@@ -2957,7 +2957,7 @@ \subsubsection{Flow filter}\label{sec:Device Types / Network Device / Device Ope
\begin{lstlisting}
struct virtio_net_ff_cap_data {
le32 groups_limit;
- le32 selectors_limit;
+ le32 classifiers_limit;
le32 rules_limit;
le32 rules_per_group_limit;
u8 last_rule_priority;
@@ -2965,7 +2965,7 @@ \subsubsection{Flow filter}\label{sec:Device Types / Network Device / Device Ope
};
\end{lstlisting}
-\field{groups_limit}, and \field{selectors_limit} represent the maximum
+\field{groups_limit}, and \field{classifiers_limit} represent the maximum
number of flow filter groups and selectors, respectively, that the driver can create.
\field{rules_limit} is the maximum number of
flow fiilter rules that the driver can create across all the groups.
@@ -3310,7 +3310,7 @@ \subsubsection{Flow filter}\label{sec:Device Types / Network Device / Device Ope
command VIRTIO_ADMIN_CMD_RESOURCE_OBJ_CREATE when the resource \field{type} is
VIRTIO_NET_RESOURCE_OBJ_FF_CLASSIFIER, if the number of flow filter selector
objects in the device exceeds the configured driver capability
-\field{selectors_limit}.
+\field{classifiers_limit}.
The device SHOULD set \field{status} to VIRTIO_ADMIN_STATUS_EBUSY for the
command VIRTIO_ADMIN_CMD_RESOURCE_OBJ_DESTROY for a flow filter group when
--
2.34.1
reply other threads:[~2025-02-15 6:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250215060633.20997-1-parav@nvidia.com \
--to=parav@nvidia.com \
--cc=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=mvaralar@redhat.com \
--cc=shahafs@nvidia.com \
--cc=virtio-comment@lists.linux.dev \
/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