From: "Michael S. Tsirkin" <mst@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>
Cc: qemu-devel@nongnu.org, Stefano Brivio <sbrivio@redhat.com>,
David Gibson <david@gibson.dropbear.id.au>,
Jason Wang <jasowang@redhat.com>
Subject: Re: [PATCH v2 0/2] virtio-net: re-arm/re-schedule when tx_burst stops virtio_net_flush_tx()
Date: Wed, 26 Oct 2022 16:23:04 -0400 [thread overview]
Message-ID: <20221026162244-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20221014132004.114602-1-lvivier@redhat.com>
On Fri, Oct 14, 2022 at 03:20:02PM +0200, Laurent Vivier wrote:
> When virtio_net_flush_tx() reaches the tx_burst value all the queue is
> not flushed and nothing restart the timer or the bottom half function.
>
> For BH, this is only missing in the virtio_net_tx_complete() function.
> For the timer, the same fix is needed in virtio_net_tx_complete() but
> it must be also managed in the TX timer function.
>
> v2:
> - fix also tx timer
Jason's area, and he wants a small nit fixed.
Looks good to me overall:
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
> Laurent Vivier (2):
> virtio-net: fix bottom-half packet TX on asynchronous completion
> virtio-net: fix TX timer with tx_burst
>
> hw/net/virtio-net.c | 68 +++++++++++++++++++++++++++++++++++++--------
> 1 file changed, 56 insertions(+), 12 deletions(-)
>
> --
> 2.37.3
>
prev parent reply other threads:[~2022-10-26 20:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 13:20 [PATCH v2 0/2] virtio-net: re-arm/re-schedule when tx_burst stops virtio_net_flush_tx() Laurent Vivier
2022-10-14 13:20 ` [PATCH v2 1/2] virtio-net: fix bottom-half packet TX on asynchronous completion Laurent Vivier
2022-10-14 13:20 ` [PATCH v2 2/2] virtio-net: fix TX timer with tx_burst Laurent Vivier
2022-10-20 4:20 ` Jason Wang
2022-10-26 20:23 ` Michael S. Tsirkin [this message]
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=20221026162244-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=jasowang@redhat.com \
--cc=lvivier@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sbrivio@redhat.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;
as well as URLs for NNTP newsgroup(s).