All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: "Dhanoa, Kully" <kully.dhanoa@intel.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	"virtio-dev@lists.oasis-open.org"
	<virtio-dev@lists.oasis-open.org>
Subject: Re: [virtio-dev] Re: [PATCH RFC] packed ring layout spec v4
Date: Fri, 10 Nov 2017 15:39:09 +0000	[thread overview]
Message-ID: <20171110153909.GA18280@stefanha-x1.localdomain> (raw)
In-Reply-To: <4DCA102C9749C849A7B61D9934ED625207A180C2@fmsmsx122.amr.corp.intel.com>

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

On Fri, Nov 10, 2017 at 03:08:16PM +0000, Dhanoa, Kully wrote:
> Hi Michael
> 
> I have embedded my comments in the packed ring layout spec attached

Hi Kully,
Is there any way you could post your comments as inline text in emails
so the discussion can continue in email messages instead of attachments?

It's hard to follow or search comments posted in documents in
attachments with most email clients.

Thanks,
Stefan

> 
> Thanks
> Kully
> 
> -----Original Message-----
> From: virtio-dev@lists.oasis-open.org [mailto:virtio-dev@lists.oasis-open.org] On Behalf Of Michael S. Tsirkin
> Sent: Wednesday, November 8, 2017 12:31 PM
> To: virtio-dev@lists.oasis-open.org
> Subject: [virtio-dev] Re: [PATCH RFC] packed ring layout spec v4
> 
> 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
> ---------------------------------------------------------------------
> Intel Corporation (UK) Limited
> Registered No. 1134945 (England)
> Registered Office: Pipers Way, Swindon SN3 1RJ
> VAT No: 860 2173 47
> 
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.


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


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

  reply	other threads:[~2017-11-10 15:39 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 ` [virtio-dev] " Michael S. Tsirkin
2017-11-10 15:08   ` Dhanoa, Kully
2017-11-10 15:39     ` Stefan Hajnoczi [this message]
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=20171110153909.GA18280@stefanha-x1.localdomain \
    --to=stefanha@redhat.com \
    --cc=kully.dhanoa@intel.com \
    --cc=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 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.