All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alvaro Karsz <alvaro.karsz@solid-run.com>
To: Hannes Reinecke <hare@suse.de>
Cc: virtualization <virtualization@lists.linux-foundation.org>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: Virtio-net - add timeouts to control commands
Date: Wed, 24 Aug 2022 12:48:25 +0300	[thread overview]
Message-ID: <CAJs=3_AW1-SVOOg8MT65KxtrZs7ikJ6DZ3xXSQZX07jA8VBr1g@mail.gmail.com> (raw)
In-Reply-To: <bedae890-80e6-9777-caff-98749d46ba3b@suse.de>

> Quite the contrary.
> There is no guarantee that a completion for a given command will be
> signaled at all; if the completion is never posted to the virtio queue
> the VM will spin forever.
>
> This is a simplistic approach. _Any_ command sent via virtio will have
> to have some sort of handling in the host, so an immediate response is
> not guaranteed.
> Especially virtio-block command will _not_ be handled immediately.


I'm referring to virtnet control commands.
virtnet_send_command is a blocking function, and returns once a
response is received for the sent control command.
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

  reply	other threads:[~2022-08-24  9:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-24  7:51 Virtio-net - add timeouts to control commands Alvaro Karsz
2022-08-24  9:06 ` Jason Wang
2022-08-24  9:16   ` Alvaro Karsz
2022-08-24  9:24     ` Hannes Reinecke
2022-08-24  9:48       ` Alvaro Karsz [this message]
2022-08-25  2:27     ` Jason Wang
2022-08-24  9:21   ` Hannes Reinecke
2022-08-24  9:42     ` Alvaro Karsz
2022-08-24 10:19       ` Hannes Reinecke
2022-08-24 10:31         ` Alvaro Karsz
2022-08-25  3:01       ` Jason Wang

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='CAJs=3_AW1-SVOOg8MT65KxtrZs7ikJ6DZ3xXSQZX07jA8VBr1g@mail.gmail.com' \
    --to=alvaro.karsz@solid-run.com \
    --cc=hare@suse.de \
    --cc=mst@redhat.com \
    --cc=virtualization@lists.linux-foundation.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 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.