From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alvaro Karsz <alvaro.karsz@solid-run.com>
Cc: virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org, jasowang@redhat.com
Subject: [virtio-comment] Re: [PATCH v2] virtio_net: support low and high rate of notification coalescing
Date: Mon, 16 Jan 2023 11:01:38 -0500 [thread overview]
Message-ID: <20230116110048-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAJs=3_BwHAuJHPEMvLUOQJ=Xm4eOoovP+4fMKqYeO06W74Dsiw@mail.gmail.com>
On Mon, Jan 16, 2023 at 04:32:11PM +0200, Alvaro Karsz wrote:
> ping
You only posted v2 Wednesday, that's just 2 days for people to review.
Sit tight next time pls :)
--
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-01-16 16:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 15:21 [virtio-dev] [PATCH v2] virtio_net: support low and high rate of notification coalescing Alvaro Karsz
2023-01-11 18:21 ` [virtio-dev] " Alvaro Karsz
2023-01-16 14:32 ` Alvaro Karsz
2023-01-16 16:01 ` Michael S. Tsirkin [this message]
2023-01-16 15:59 ` Michael S. Tsirkin
2023-01-17 12:42 ` [virtio-comment] " Alvaro Karsz
2023-01-16 19:42 ` [virtio-dev] " Parav Pandit
2023-01-16 20:33 ` Michael S. Tsirkin
2023-01-16 20:52 ` [virtio-comment] " Parav Pandit
2023-01-16 21:30 ` Michael S. Tsirkin
2023-01-17 0:07 ` [virtio-comment] " Parav Pandit
2023-01-17 0:27 ` Michael S. Tsirkin
2023-01-17 3:49 ` [virtio-comment] " Parav Pandit
2023-01-17 13:03 ` [virtio-comment] " Alvaro Karsz
2023-01-17 15:18 ` Michael S. Tsirkin
2023-02-06 8:10 ` Alvaro Karsz
2023-01-17 12:44 ` Alvaro Karsz
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=20230116110048-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alvaro.karsz@solid-run.com \
--cc=jasowang@redhat.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