All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Cc: stefanha@redhat.com, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-2.4] virtio-net: Flush incoming queues when DRIVER_OK is being set
Date: Wed, 15 Jul 2015 15:24:11 +0800	[thread overview]
Message-ID: <55A60A9B.70902@redhat.com> (raw)
In-Reply-To: <1436929347-11991-1-git-send-email-famz@redhat.com>



On 07/15/2015 11:02 AM, Fam Zheng wrote:
> This patch fixes network hang after "stop" then "cont", while network
> packets keep arriving.
>
> Tested both manually (tap, host pinging guest) and with Jason's qtest
> series (plus his "[PATCH 2.4] socket: pass correct size in
> net_socket_send()" fix).
>
> As virtio_net_set_status is called when guest driver is setting status
> byte and when vm state is changing, it is a good opportunity to flush
> queued packets.
>
> This is necessary because during vm stop the backend (e.g. tap) would
> stop rx processing after .can_receive returns false, until the queue is
> explicitly flushed or purged.
>
> The other interesting condition in .can_receive, virtio_queue_ready(),
> is handled by virtio_net_handle_rx() when guest kicks; the 3rd condition
> is invalid queue index which doesn't need flushing.
>
> Signed-off-by: Fam Zheng <famz@redhat.com>
>
> ---

Reviewed-by: Jason Wang <jasowang@redhat.com>

btw, there's another condition in can_receive() which is suspicious:

...
    if (nc->queue_index >= n->curr_queues) {
        return 0;
    }
...

This requires queue to be flushed when the number of queues was
increased. But it looks unnecessary since both guest and vhost does not
care about this. So I think we could safely just remove this condition.
Maybe a patch on top.

Thanks

>
> v2: Limit to "virtio_net_started(n, queue_status) &&
>     !n->vhost_started".[MST]
> ---
>  hw/net/virtio-net.c | 10 +++++++++-
>  1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/hw/net/virtio-net.c b/hw/net/virtio-net.c
> index d728233..24c7be1 100644
> --- a/hw/net/virtio-net.c
> +++ b/hw/net/virtio-net.c
> @@ -162,6 +162,8 @@ static void virtio_net_set_status(struct VirtIODevice *vdev, uint8_t status)
>      virtio_net_vhost_status(n, status);
>  
>      for (i = 0; i < n->max_queues; i++) {
> +        NetClientState *ncs = qemu_get_subqueue(n->nic, i);
> +        bool queue_started;
>          q = &n->vqs[i];
>  
>          if ((!n->multiqueue && i != 0) || i >= n->curr_queues) {
> @@ -169,12 +171,18 @@ static void virtio_net_set_status(struct VirtIODevice *vdev, uint8_t status)
>          } else {
>              queue_status = status;
>          }
> +        queue_started =
> +            virtio_net_started(n, queue_status) && !n->vhost_started;
> +
> +        if (queue_started) {
> +            qemu_flush_queued_packets(ncs);
> +        }
>  
>          if (!q->tx_waiting) {
>              continue;
>          }
>  
> -        if (virtio_net_started(n, queue_status) && !n->vhost_started) {
> +        if (queue_started) {
>              if (q->tx_timer) {
>                  timer_mod(q->tx_timer,
>                                 qemu_clock_get_ns(QEMU_CLOCK_VIRTUAL) + n->tx_timeout);

  parent reply	other threads:[~2015-07-15  7:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-15  3:02 [Qemu-devel] [PATCH for-2.4] virtio-net: Flush incoming queues when DRIVER_OK is being set Fam Zheng
2015-07-15  6:52 ` Wen Congyang
2015-07-15  7:24 ` Jason Wang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-07-14  9:41 Fam Zheng
2015-07-14 10:09 ` Michael S. Tsirkin
2015-07-14 10:17   ` Fam Zheng

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=55A60A9B.70902@redhat.com \
    --to=jasowang@redhat.com \
    --cc=famz@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.