From: Cornelia Huck <cohuck@redhat.com>
To: Parav Pandit <parav@nvidia.com>,
virtio-comment@lists.oasis-open.org, mst@redhat.com
Cc: sburla@marvell.com, shahafs@nvidia.com, si-wei.liu@oracle.com,
xuanzhuo@linux.alibaba.com, Parav Pandit <parav@nvidia.com>,
Heng Qi <hengqi@linux.alibaba.com>
Subject: [virtio-comment] Re: [PATCH v6 3/5] virtio-net: Add flow filter group life cycle commands
Date: Wed, 22 Nov 2023 14:42:13 +0100 [thread overview]
Message-ID: <874jhdlxai.fsf@redhat.com> (raw)
In-Reply-To: <20231110123853.2093309-4-parav@nvidia.com>
On Fri, Nov 10 2023, Parav Pandit <parav@nvidia.com> wrote:
> @@ -2596,6 +2606,32 @@ \subsubsection{Control Virtqueue}\label{sec:Device Types / Network Device / Devi
> Each array entry of \field{types} represents supported match fields of
> the packet by the device.
>
> +\subparagraph{Flow Filter Group Add}\label{sec:Device Types / Network Device / Device Operation / Control Virtqueue / Flow Filter / Flow Filter Group Add}
> +
> +The command VIRTIO_NET_CTRL_FF_GROUP_ADD adds a new flow filter
> +group with the supplied group identifier \field{id} with assigned
> +priority \field{priority}.
> +
> +\begin{lstlisting}
> +struct virtio_net_ctrl_ff_group_add {
> + le16 priority; /* higher the value, higher priority */
> + le16 id;
> +};
> +\end{lstlisting}
> +
> +\subparagraph{Flow Filter Group Delete}\label{sec:Device Types / Network Device / Device Operation / Control Virtqueue / Flow Filter / Flow Filter Group Delete}
> +
> +The command VIRTIO_NET_CTRL_FF_GROUP_DEL deletes the
> +flow filter group that has been previously added using command
> +VIRTIO_NET_CTRL_FF_GROUP_ADD. Flow filter group is
> +identified using a group identifier \field{id}.
"The command VIRTIO_NET_CTRL_FF_GROUP_DEL deletes the flow filter group
identified by the group identifier \field{id} previously added using the
command VIRTIO_NET_CTRL_FF_GROUP_ADD."
> +
> +\begin{lstlisting}
> +struct virtio_net_ctrl_ff_group_del {
> + le16 id;
> +};
> +\end{lstlisting}
> +
> \subsubsection{Legacy Interface: Framing Requirements}\label{sec:Device
> Types / Network Device / Legacy Interface: Framing Requirements}
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 prev parent reply other threads:[~2023-11-22 13:42 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 12:38 [virtio-comment] [PATCH v6 0/5] virtio-net: Support flow filter for receive packets Parav Pandit
2023-11-10 12:38 ` [virtio-comment] [PATCH v6 1/5] virtio-net: Add theory of operation for flow filter Parav Pandit
2023-11-22 13:22 ` [virtio-comment] " Cornelia Huck
2023-11-22 13:30 ` [virtio-comment] " Parav Pandit
2023-11-10 12:38 ` [virtio-comment] [PATCH v6 2/5] virtio-net: Add flow filter capabilities read commands Parav Pandit
2023-11-22 13:38 ` [virtio-comment] " Cornelia Huck
2023-11-22 13:44 ` [virtio-comment] " Parav Pandit
2023-11-22 14:02 ` [virtio-comment] " Michael S. Tsirkin
2023-11-22 14:10 ` [virtio-comment] " Parav Pandit
2023-11-22 14:51 ` [virtio-comment] " Michael S. Tsirkin
2023-11-22 15:00 ` [virtio-comment] " Parav Pandit
2023-11-24 4:02 ` [virtio-comment] " Jason Wang
2023-11-24 4:13 ` Parav Pandit
2023-11-24 5:31 ` Michael S. Tsirkin
2023-11-24 5:40 ` Parav Pandit
2023-11-24 6:02 ` Jason Wang
2023-11-24 6:41 ` Parav Pandit
2023-11-24 9:13 ` Michael S. Tsirkin
2023-11-27 10:19 ` Parav Pandit
2023-11-27 11:10 ` Michael S. Tsirkin
2023-11-27 11:12 ` Parav Pandit
2023-11-27 12:52 ` Michael S. Tsirkin
2023-11-27 12:58 ` Parav Pandit
2023-11-27 13:05 ` Michael S. Tsirkin
2023-11-24 6:18 ` Michael S. Tsirkin
2023-11-24 6:31 ` Parav Pandit
2023-11-24 11:33 ` Michael S. Tsirkin
2023-11-27 10:19 ` Parav Pandit
2023-11-27 11:28 ` Michael S. Tsirkin
2023-11-27 11:40 ` Parav Pandit
2023-11-27 11:47 ` Michael S. Tsirkin
2023-11-27 11:54 ` Parav Pandit
2023-11-27 12:42 ` Michael S. Tsirkin
2023-11-27 13:05 ` Parav Pandit
2023-11-27 13:12 ` Michael S. Tsirkin
2023-11-27 13:06 ` Cornelia Huck
2023-11-27 13:14 ` Michael S. Tsirkin
2023-11-24 6:03 ` Jason Wang
2023-11-24 5:32 ` Michael S. Tsirkin
2023-11-24 5:53 ` Parav Pandit
2023-11-24 6:06 ` Michael S. Tsirkin
2023-11-24 6:27 ` Parav Pandit
2023-11-24 10:27 ` Michael S. Tsirkin
2023-11-27 10:19 ` Parav Pandit
2023-11-27 11:37 ` Michael S. Tsirkin
2023-11-27 11:47 ` Parav Pandit
2023-12-12 15:52 ` Michael S. Tsirkin
2023-12-13 4:48 ` Jason Wang
2023-11-10 12:38 ` [virtio-comment] [PATCH v6 3/5] virtio-net: Add flow filter group life cycle commands Parav Pandit
2023-11-22 13:42 ` Cornelia Huck [this message]
2023-11-10 12:38 ` [virtio-comment] [PATCH v6 4/5] virtio-net: Add flow filter match entry, action and requests Parav Pandit
2023-11-22 13:52 ` [virtio-comment] " Cornelia Huck
2023-11-10 12:38 ` [virtio-comment] [PATCH v6 5/5] virtio-net: Add flow filter device and driver requirements Parav Pandit
2023-11-20 6:47 ` [virtio-comment] RE: [PATCH v6 0/5] virtio-net: Support flow filter for receive packets Parav Pandit
2023-11-21 12:54 ` Parav Pandit
2023-11-22 11:26 ` Cornelia Huck
2023-11-22 12:03 ` Parav Pandit
2023-11-23 10:22 ` Parav Pandit
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=874jhdlxai.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=hengqi@linux.alibaba.com \
--cc=mst@redhat.com \
--cc=parav@nvidia.com \
--cc=sburla@marvell.com \
--cc=shahafs@nvidia.com \
--cc=si-wei.liu@oracle.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=xuanzhuo@linux.alibaba.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 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.