Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: Parav Pandit <parav@nvidia.com>
To: mst@redhat.com, virtio-dev@lists.oasis-open.org, cohuck@redhat.com
Cc: virtio-comment@lists.oasis-open.org, shahafs@nvidia.com,
	Parav Pandit <parav@nvidia.com>
Subject: [PATCH] virtio-net: Improve control vq introductory description
Date: Mon, 23 Jan 2023 03:16:51 +0200	[thread overview]
Message-ID: <20230123011651.804147-1-parav@nvidia.com> (raw)

The control VQ of the virtio network device is used for controlling
multiple features, not just advanced steering control. The control VQ
dynamically changes multiple features of the initialized device.

Hence, update this area of control VQ introductory description.

This patch is on top of [1].

[1] https://lists.oasis-open.org/archives/virtio-dev/202301/msg00272.html

Fixes: https://github.com/oasis-tcs/virtio-spec/issues/156
Signed-off-by: Parav Pandit <parav@nvidia.com>
---
 device-types/net/description.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/device-types/net/description.tex b/device-types/net/description.tex
index 41ae7f5..56bd672 100644
--- a/device-types/net/description.tex
+++ b/device-types/net/description.tex
@@ -8,7 +8,7 @@ \section{Network Device}\label{sec:Device Types / Network Device}
 device. Empty buffers are placed in one virtqueue for receiving
 packets, and outgoing packets are enqueued into another for
 transmission in that order. A third command queue is used to
-control advanced filtering features.
+dynamically manipulate various features of the initialized device.
 
 \subsection{Device ID}\label{sec:Device Types / Network Device / Device ID}
 
-- 
2.26.2


             reply	other threads:[~2023-01-23  1:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-23  1:16 Parav Pandit [this message]
2023-01-23 11:49 ` [virtio-comment] Re: [PATCH] virtio-net: Improve control vq introductory description Cornelia Huck
2023-01-23 12:21   ` 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=20230123011651.804147-1-parav@nvidia.com \
    --to=parav@nvidia.com \
    --cc=cohuck@redhat.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