From: Stefan Hajnoczi <stefanha@gmail.com>
To: elohimes@gmail.com
Cc: mst@redhat.com, marcandre.lureau@redhat.com, berrange@redhat.com,
jasowang@redhat.com, maxime.coquelin@redhat.com,
yury-kotov@yandex-team.ru, wrfsh@yandex-team.ru,
qemu-devel@nongnu.org, zhangyu31@baidu.com, chaiwen@baidu.com,
nixun@baidu.com, lilin24@baidu.com,
Xie Yongji <xieyongji@baidu.com>
Subject: Re: [Qemu-devel] [PATCH v5 1/6] vhost-user: Support transferring inflight buffer between qemu and backend
Date: Tue, 29 Jan 2019 12:11:55 +0800 [thread overview]
Message-ID: <20190129041155.GG3264@stefanha-x1.localdomain> (raw)
In-Reply-To: <20190122083152.10705-2-xieyongji@baidu.com>
[-- Attachment #1: Type: text/plain, Size: 1385 bytes --]
On Tue, Jan 22, 2019 at 04:31:47PM +0800, elohimes@gmail.com wrote:
> +typedef struct DescState {
> + uint8_t inuse;
> + uint8_t version;
> + uint16_t used_idx;
> + uint16_t avail_idx;
> + uint16_t reserved;
> +} DescState;
> +
> +typedef struct QueueRegion {
> + uint8_t valid;
> + uint16_t desc_num;
> + DescState desc[0];
> +} QueueRegion;
> +
> +The struct DescState is used to describe one head-descriptor's state. The
> +fields have following meanings:
> +
> + inuse: Indicate whether the descriptor is inuse or not.
> +
> + version: Indicate whether we have an atomic update to used ring and
> + inflight buffer when slave crash at that point. This field should be
> + increased by one before and after this two updates. An odd version
> + indicates an in-progress update.
> +
> + used_idx: Store old index of used ring before we update used ring and
> + inflight buffer so that slave can know whether an odd version inflight
> + head-descriptor in inflight buffer is processed or not.
> +
> + avail_idx: Used to preserve the descriptor's order in avail ring so that
> + slave can resubmit descriptors in order.
Will a completely new "packed vring" inflight shm layout be necessary to
support the packed vring layout in VIRTIO 1.1?
https://docs.oasis-open.org/virtio/virtio/v1.1/csprd01/virtio-v1.1-csprd01.html#x1-610007
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2019-01-29 4:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 8:31 [Qemu-devel] [PATCH v5 0/6] vhost-user-blk: Add support for backend reconnecting elohimes
2019-01-22 8:31 ` [Qemu-devel] [PATCH v5 1/6] vhost-user: Support transferring inflight buffer between qemu and backend elohimes
2019-01-29 4:11 ` Stefan Hajnoczi [this message]
2019-01-29 4:26 ` Michael S. Tsirkin
2019-01-29 6:15 ` Yongji Xie
2019-01-29 14:15 ` Michael S. Tsirkin
2019-01-30 2:07 ` Yongji Xie
2019-01-30 2:30 ` Michael S. Tsirkin
2019-01-30 3:49 ` Yongji Xie
2019-01-30 4:07 ` Michael S. Tsirkin
2019-01-30 4:11 ` Yongji Xie
2019-01-22 8:31 ` [Qemu-devel] [PATCH v5 2/6] libvhost-user: Introduce vu_queue_map_desc() elohimes
2019-01-22 8:31 ` [Qemu-devel] [PATCH v5 3/6] libvhost-user: Support tracking inflight I/O in shared memory elohimes
2019-01-30 2:31 ` Jason Wang
2019-01-30 3:14 ` Michael S. Tsirkin
2019-01-30 9:52 ` Jason Wang
2019-01-30 3:58 ` Yongji Xie
2019-02-01 2:26 ` Jason Wang
2019-01-30 5:48 ` Yongji Xie
2019-02-01 2:27 ` Jason Wang
2019-02-05 1:37 ` Yongji Xie
2019-01-22 8:31 ` [Qemu-devel] [PATCH v5 4/6] vhost-user-blk: Add support to get/set inflight buffer elohimes
2019-01-22 8:31 ` [Qemu-devel] [PATCH v5 5/6] vhost-user-blk: Add support to reconnect backend elohimes
2019-01-22 8:31 ` [Qemu-devel] [PATCH v5 6/6] contrib/vhost-user-blk: enable inflight I/O tracking elohimes
2019-01-30 2:29 ` [Qemu-devel] [PATCH v5 0/6] vhost-user-blk: Add support for backend reconnecting Jason Wang
2019-01-30 3:40 ` 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=20190129041155.GG3264@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=berrange@redhat.com \
--cc=chaiwen@baidu.com \
--cc=elohimes@gmail.com \
--cc=jasowang@redhat.com \
--cc=lilin24@baidu.com \
--cc=marcandre.lureau@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=mst@redhat.com \
--cc=nixun@baidu.com \
--cc=qemu-devel@nongnu.org \
--cc=wrfsh@yandex-team.ru \
--cc=xieyongji@baidu.com \
--cc=yury-kotov@yandex-team.ru \
--cc=zhangyu31@baidu.com \
/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;
as well as URLs for NNTP newsgroup(s).