Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: virtio-dev@lists.oasis-open.org
Subject: [virtio-dev] Re: [PATCH RFC] packed ring layout spec v4
Date: Wed, 8 Nov 2017 14:30:50 +0200	[thread overview]
Message-ID: <20171108142820-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20171108141659-mutt-send-email-mst@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 451 bytes --]

On Wed, Nov 08, 2017 at 02:28:10PM +0200, Michael S. Tsirkin wrote:
> Below is an attempt at a formal write-up of the latest proposal
> with some modifications. Will reply with a pdf version
> as well.
> 
> This is reasonably complete functionally, from spec point of
> view we need
> - more conformance statements
> - pseudo-code
> - discussion of memory barriers
> - rearrange existing (1.0) layout discussion to make it fit
>   in a single chapter

[-- Attachment #2: draft.pdf --]
[-- Type: application/pdf, Size: 387995 bytes --]

[-- Attachment #3: Type: text/plain, Size: 208 bytes --]


---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org

  reply	other threads:[~2017-11-08 12:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-08 12:28 [virtio-dev] [PATCH RFC] packed ring layout spec v4 Michael S. Tsirkin
2017-11-08 12:30 ` Michael S. Tsirkin [this message]
2017-11-10 15:08   ` [virtio-dev] " Dhanoa, Kully
2017-11-10 15:39     ` Stefan Hajnoczi
2017-11-22 14:57     ` Michael S. Tsirkin
2017-11-10 11:40 ` [virtio-dev] " Stefan Hajnoczi
2017-11-16 10:44 ` Lars Ganrot
2017-11-24 10:00 ` [virtio-dev] [PATCH RFC] packed ring layout spec v5 Dhanoa, Kully
2017-11-24 16:28   ` Michael S. Tsirkin
2017-11-28  3:26   ` Michael S. Tsirkin
2017-11-25 19:55 ` Lars Ganrot
2017-11-28 14:36   ` Michael S. Tsirkin
2017-11-29  8:12     ` Lars Ganrot

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=20171108142820-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=virtio-dev@lists.oasis-open.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox