From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vlad Zolotarov Subject: virtio specification: OOO completion of the xmit buffers in the networking device Date: Mon, 02 Jun 2014 16:33:33 +0300 Message-ID: <538C7D2D.8080508@cloudius-systems.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit To: rusty@rustcorp.com.au, kvm@vger.kernel.org Return-path: Received: from mail-we0-f173.google.com ([74.125.82.173]:39046 "EHLO mail-we0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754327AbaFBNdk (ORCPT ); Mon, 2 Jun 2014 09:33:40 -0400 Received: by mail-we0-f173.google.com with SMTP id u57so5149440wes.18 for ; Mon, 02 Jun 2014 06:33:38 -0700 (PDT) Sender: kvm-owner@vger.kernel.org List-ID: 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