public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Vlad Zolotarov <vladz@cloudius-systems.com>
To: rusty@rustcorp.com.au, kvm@vger.kernel.org
Subject: virtio specification: OOO completion of the xmit buffers in the networking device
Date: Mon, 02 Jun 2014 16:33:33 +0300	[thread overview]
Message-ID: <538C7D2D.8080508@cloudius-systems.com> (raw)

Rusty, hi!
I'd like to ask for a small clarification about the virtio spec.
The virtio specification is put the way that it allows the out-of-order 
completions in general. Although it states that it's mostly relevant to 
the virtio-blk it doesn't explicitly bans it for virtio networking 
devices (for generality?).

(AFAICS the current virtio HV implementations make sure there is no OOO 
Tx buffers completions).

I wonder if this feature (OOO Tx buffers completions) seems practical to 
u and if not can I hope that it could be clearly stated in the future 
virtio specification releases that it's forbidden?

thanks in advance,
vlad


             reply	other threads:[~2014-06-02 13:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-02 13:33 Vlad Zolotarov [this message]
2014-06-04  3:52 ` virtio specification: OOO completion of the xmit buffers in the networking device Rusty Russell
2014-06-04 18:54   ` 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=538C7D2D.8080508@cloudius-systems.com \
    --to=vladz@cloudius-systems.com \
    --cc=kvm@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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