From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alvaro Karsz <alvaro.karsz@solid-run.com>
Cc: Heng Qi <hengqi@linux.alibaba.com>,
virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org, Parav Pandit <parav@nvidia.com>,
Jason Wang <jasowang@redhat.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Subject: [virtio-comment] Re: [PATCH v2] virtio-net: support the virtqueue coalescing moderation
Date: Fri, 10 Feb 2023 04:39:59 -0500 [thread overview]
Message-ID: <20230210043841-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAJs=3_Bz_NECj4nUtu5es=UECD9c1FAKy1SFtKrve8BL4KDDVA@mail.gmail.com>
On Fri, Feb 10, 2023 at 11:30:40AM +0200, Alvaro Karsz wrote:
> > > \devicenormative{\subparagraph}{Notifications Coalescing}{Device Types / Network Device / Device Operation / Control Virtqueue / Notifications Coalescing}
> > >
> > > -A device SHOULD respond to the VIRTIO_NET_CTRL_NOTF_COAL commands with VIRTIO_NET_ERR if it was not able to change the parameters.
> > > +A device SHOULD respond to the VIRTIO_NET_CTRL_NOTF_COAL commands with VIRTIO_NET_ERR if it was not able to change the parameters or
> > > +was not able to find a virtqueue using the \field{vqn}.
> >
> > First please create multiple statements not a single long one.
> > Second vqn only exists for per vq commands so create a statement
> > just for that.
> > Also more explicit please. What does this mean? I suspect that vq was not
> > enabled?
> > Also, we MUST have vqn < max_virtqueue_pairs.
> >
>
> I believe that you meant vqn < max_virtqueue_pairs * 2
Yes thanks!
Just pls snip to just the text you qoute to just relevant parts -
I had to scroll like 300 lines to get to the relevant one :)
--
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 prev parent reply other threads:[~2023-02-10 9:39 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 7:01 [virtio-comment] [PATCH v2] virtio-net: support the virtqueue coalescing moderation Heng Qi
2023-02-10 8:38 ` [virtio-comment] " Michael S. Tsirkin
2023-02-10 9:30 ` [virtio-dev] " Alvaro Karsz
2023-02-10 9:39 ` Michael S. Tsirkin [this message]
2023-02-10 9:53 ` [virtio-comment] " Heng Qi
2023-02-10 10:29 ` [virtio-dev] " Michael S. Tsirkin
2023-02-10 11:19 ` [virtio-comment] " Heng Qi
2023-02-12 20:47 ` Michael S. Tsirkin
2023-02-13 2:36 ` Heng Qi
2023-02-13 8:17 ` Michael S. Tsirkin
2023-02-10 9:22 ` [virtio-comment] " Alvaro Karsz
2023-02-10 9:38 ` Michael S. Tsirkin
2023-02-10 10:00 ` Heng Qi
2023-02-10 10:16 ` [virtio-dev] " Alvaro Karsz
2023-02-10 11:24 ` Heng Qi
2023-02-10 10:31 ` Michael S. Tsirkin
2023-02-10 11:29 ` Heng Qi
2023-02-10 9:57 ` [virtio-comment] Re: [virtio-dev] " Heng Qi
2023-02-10 19:36 ` [virtio-comment] " Parav Pandit
2023-02-11 2:01 ` [virtio-comment] Re: [virtio-dev] " Heng Qi
2023-02-11 8:45 ` [virtio-comment] " Alvaro Karsz
2023-02-11 9:42 ` Alvaro Karsz
2023-02-11 10:00 ` Heng Qi
2023-02-11 10:18 ` Alvaro Karsz
2023-02-11 13:57 ` Parav Pandit
2023-02-11 15:46 ` Alvaro Karsz
2023-02-11 15:57 ` [virtio-dev] " Parav Pandit
2023-02-11 16:13 ` Alvaro Karsz
2023-02-11 16:22 ` Parav Pandit
2023-02-13 3:13 ` Heng Qi
2023-02-12 20:23 ` [virtio-dev] " Michael S. Tsirkin
2023-02-12 20:53 ` Alvaro Karsz
2023-02-12 21:08 ` [virtio-dev] " Michael S. Tsirkin
2023-02-11 13:47 ` [virtio-comment] " Parav Pandit
2023-02-12 9:35 ` [virtio-comment] " Michael S. Tsirkin
2023-02-13 3:17 ` Heng Qi
2023-02-13 2:52 ` Heng Qi
2023-02-12 20:43 ` [virtio-dev] " Michael S. Tsirkin
2023-02-13 3:21 ` [virtio-comment] " 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=20230210043841-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alvaro.karsz@solid-run.com \
--cc=hengqi@linux.alibaba.com \
--cc=jasowang@redhat.com \
--cc=parav@nvidia.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox