From: Stefan Hajnoczi <stefanha@redhat.com>
To: Coiby Xu <coiby.xu@gmail.com>
Cc: kwolf@redhat.com, bharatlkmlkvm@gmail.com, qemu-devel@nongnu.org,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [PATCH v4 0/5] vhost-user block device backend implementation
Date: Wed, 19 Feb 2020 16:38:15 +0000 [thread overview]
Message-ID: <20200219163815.GD1085125@stefanha-x1.localdomain> (raw)
In-Reply-To: <20200218050711.8133-1-coiby.xu@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 683 bytes --]
On Tue, Feb 18, 2020 at 01:07:06PM +0800, Coiby Xu wrote:
> v4:
> * add object properties in class_init
> * relocate vhost-user-blk-test
> * other changes including using SocketAddress, coding style, etc.
Thanks! I think the vhost-user server code can be simplified if
libvhost-user uses the event loop for asynchronous socket I/O. Then
it's no longer necessary to duplicate vu_message_read() and
vu_kick_cb(). I've replied to Patch 1 and we can discuss on IRC if you
want to chat about it.
I've also CCed Marc-André to see what he thinks about removing the
blocking recv from libvhost-user and instead using the event loop (just
like for eventfds).
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-02-19 18:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 5:07 [PATCH v4 0/5] vhost-user block device backend implementation Coiby Xu
2020-02-18 5:07 ` [PATCH v4 1/5] extend libvhost to support IOThread and coroutine Coiby Xu
2020-02-19 16:33 ` Stefan Hajnoczi
2020-02-25 14:55 ` Kevin Wolf
2020-02-18 5:07 ` [PATCH v4 2/5] generic vhost user server Coiby Xu
2020-02-25 15:44 ` Kevin Wolf
2020-02-28 4:23 ` Coiby Xu
2020-02-18 5:07 ` [PATCH v4 3/5] vhost-user block device backend server Coiby Xu
2020-02-25 16:09 ` Kevin Wolf
2020-02-18 5:07 ` [PATCH v4 4/5] a standone-alone tool to directly share disk image file via vhost-user protocol Coiby Xu
2020-02-18 5:07 ` [PATCH v4 5/5] new qTest case to test the vhost-user-blk-server Coiby Xu
2020-02-19 16:38 ` Stefan Hajnoczi [this message]
2020-02-26 15:18 ` [PATCH v4 0/5] vhost-user block device backend implementation Coiby Xu
2020-02-27 7:41 ` Stefan Hajnoczi
2020-02-27 9:53 ` Coiby Xu
2020-02-27 10:02 ` Kevin Wolf
2020-02-27 10:28 ` Coiby Xu
2020-02-27 10:55 ` Kevin Wolf
2020-02-27 11:07 ` Marc-André Lureau
2020-02-27 11:19 ` Kevin Wolf
2020-02-27 11:38 ` Daniel P. Berrangé
2020-02-27 13:07 ` Marc-André Lureau
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=20200219163815.GD1085125@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=bharatlkmlkvm@gmail.com \
--cc=coiby.xu@gmail.com \
--cc=kwolf@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.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.