From: "Michael S. Tsirkin" <mst@redhat.com>
To: thomas <east.moutain.yang@gmail.com>
Cc: qemu-devel@nongnu.org, jasowang@redhat.com
Subject: Re: [PATCH] Update event idx if guest has made extra buffers during double check
Date: Mon, 17 Jun 2024 06:58:29 -0400 [thread overview]
Message-ID: <20240617065455-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20240613022147.5886-1-east.moutain.yang@gmail.com>
Thanks for the patch!
Yet something to improve:
subject should list the affected component, and be shorter.
On Thu, Jun 13, 2024 at 10:21:47AM +0800, thomas wrote:
> Fixes: 06b12970174 ("virtio-net: fix network stall under load")
this should come at the end. and what exactly does this
refer to? did this commit cause a regression of some sort?
> If guest has made some buffers available during double check,
what does "double check" refer to?
> but the total buffer size available is lower than @bufsize,
> notify the guest with the latest available idx(event idx)
> seen by the host.
which makes sense why? And which changes the correct behavious of what
to a new behaviour of what which is better why?
Pls review docs/devel/submitting-a-patch.rst and follow the
process there.
> ---
> hw/net/virtio-net.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/hw/net/virtio-net.c b/hw/net/virtio-net.c
> index 9c7e85caea..23c6c8c898 100644
> --- a/hw/net/virtio-net.c
> +++ b/hw/net/virtio-net.c
> @@ -1654,6 +1654,7 @@ static int virtio_net_has_buffers(VirtIONetQueue *q, int bufsize)
> if (virtio_queue_empty(q->rx_vq) ||
> (n->mergeable_rx_bufs &&
> !virtqueue_avail_bytes(q->rx_vq, bufsize, 0))) {
> + virtio_queue_set_notification(q->rx_vq, 1);
> return 0;
> }
> }
> --
> 2.39.0
next prev parent reply other threads:[~2024-06-17 10:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 2:21 [PATCH] Update event idx if guest has made extra buffers during double check thomas
2024-06-17 2:15 ` Jason Wang
2024-06-17 10:58 ` Michael S. Tsirkin [this message]
2024-06-17 13:51 ` Yang Dongshan
2024-06-24 10:24 ` Michael S. Tsirkin
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=20240617065455-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=east.moutain.yang@gmail.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).