From: "Michael S. Tsirkin" <mst@redhat.com>
To: Ilya Lesokhin <ilyal@mellanox.com>
Cc: "virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>
Subject: [virtio-dev] Re: packed ring layout proposal v3
Date: Mon, 30 Oct 2017 04:08:46 +0200 [thread overview]
Message-ID: <20171030040341-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <AM4PR0501MB272332C92A384C97D6975D8DD4580@AM4PR0501MB2723.eurprd05.prod.outlook.com>
On Sun, Oct 29, 2017 at 02:34:56PM +0000, Ilya Lesokhin wrote:
> > -----Original Message-----
> > From: Michael S. Tsirkin [mailto:mst@redhat.com]
> > Sent: Sunday, October 29, 2017 4:22 PM
> > To: Ilya Lesokhin <ilyal@mellanox.com>
> > Cc: virtio-dev@lists.oasis-open.org; virtualization@lists.linux-foundation.org
> > Subject: Re: packed ring layout proposal v3
> >
> > If you do this whats the point of the id? Just use descriptor offset like virtio 0 did.
> >
>
> I agree that ID is pointless when requests are completed in order.
>
> But I'm not sure what you mean by descriptor offset?
Where the descriptor is within the ring.
--
MST
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2017-10-30 2:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-10 5:06 [virtio-dev] packed ring layout proposal v3 Michael S. Tsirkin
[not found] ` <240c623b-2d8f-28d9-d349-d01e2c24b93a@redhat.com>
[not found] ` <20170208214435-mutt-send-email-mst@kernel.org>
[not found] ` <cc075b18-0913-ef89-96a8-a29869abd73e@redhat.com>
[not found] ` <20170209171105.075a9d9c.cornelia.huck@de.ibm.com>
[not found] ` <20170222181333-mutt-send-email-mst@kernel.org>
[not found] ` <20170307165353.00ff80d9.cornelia.huck@de.ibm.com>
[not found] ` <20170307223057-mutt-send-email-mst@kernel.org>
2017-07-10 16:27 ` [virtio-dev] packed ring layout proposal v2 Amnon Ilan
2017-07-16 6:00 ` Lior Narkis
2017-07-18 16:23 ` Michael S. Tsirkin
2017-07-19 7:41 ` Lior Narkis
2017-07-20 13:06 ` Michael S. Tsirkin
2017-09-11 7:47 ` [virtio-dev] Re: packed ring layout proposal v3 Jason Wang
2017-09-12 16:23 ` Willem de Bruijn
2017-09-13 1:26 ` Jason Wang
2017-09-12 16:20 ` [virtio-dev] " Willem de Bruijn
2017-09-20 9:11 ` Liang, Cunming
2017-09-25 22:24 ` Michael S. Tsirkin
2017-09-26 23:38 ` Steven Luong (sluong)
2017-09-27 23:49 ` Michael S. Tsirkin
2017-09-28 9:44 ` Liang, Cunming
2017-10-01 4:08 ` Michael S. Tsirkin
[not found] ` <20171004123901.oomueufqg52uhas4@localhost.localdomain>
2017-10-04 12:58 ` Michael S. Tsirkin
2017-10-10 9:56 ` Liang, Cunming
2017-09-28 21:13 ` Michael S. Tsirkin
2017-09-21 13:36 ` Liang, Cunming
2017-09-28 21:27 ` Michael S. Tsirkin
2017-10-08 6:16 ` [virtio-dev] " Ilya Lesokhin
2017-10-25 16:20 ` [virtio-dev] " Michael S. Tsirkin
2017-10-29 9:05 ` [virtio-dev] " Ilya Lesokhin
2017-10-29 14:21 ` [virtio-dev] " Michael S. Tsirkin
2017-10-29 14:34 ` [virtio-dev] " Ilya Lesokhin
2017-10-30 2:08 ` Michael S. Tsirkin [this message]
2017-10-30 6:30 ` Ilya Lesokhin
2017-10-30 16:30 ` [virtio-dev] " 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=20171030040341-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=ilyal@mellanox.com \
--cc=virtio-dev@lists.oasis-open.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox