From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: Prerna <saxenap.ltc@gmail.com>,
Prerna Saxena <prerna.saxena@nutanix.com>,
Anil Kumar Boggarapu <anilkumar.boggarapu@nutanix.com>,
QEMU <qemu-devel@nongnu.org>,
Felipe Franciosi <felipe@nutanix.com>
Subject: Re: [Qemu-devel] [PATCH v3 0/2] vhost-user: Extend protocol to receive replies on any command.
Date: Wed, 27 Jul 2016 07:21:15 +0300 [thread overview]
Message-ID: <20160727072039-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAJ+F1CKeGOhnTp_83wUHca6nnaq37qhq6Mhtc3DUUcyUw3R8iQ@mail.gmail.com>
On Mon, Jul 25, 2016 at 02:27:18PM +0400, Marc-André Lureau wrote:
> Hi
>
> On Mon, Jul 25, 2016 at 10:41 AM, Prerna <saxenap.ltc@gmail.com> wrote:
> >
> >
> > On Thu, Jul 7, 2016 at 12:04 PM, Prerna Saxena <saxenap.ltc@gmail.com>
> > wrote:
> >>
> >> From: Prerna Saxena <prerna.saxena@nutanix.com>
> >>
> >> The current vhost-user protocol requires the client to send responses to
> >> only a
> >> few commands. For the remaining commands, it is impossible for QEMU to
> >> know the
> >> status of the requested operation -- ie, did it succeed? If so, by what
> >> time?
> >>
> >> This is inconvenient, and can also lead to races. As an example:
> >> [..snip..]
> >>
> >> References:
> >> v1 : https://lists.gnu.org/archive/html/qemu-devel/2016-06/msg07152.html
> >> v2 : https://lists.gnu.org/archive/html/qemu-devel/2016-07/msg00048.html
> >>
> >>
> >> Prerna Saxena (2):
> >> vhost-user: Introduce a new protocol feature REPLY_ACK.
> >> vhost-user: Attempt to fix a race with set_mem_table.
> >>
> >> docs/specs/vhost-user.txt | 44 +++++++++++++++
> >> hw/virtio/vhost-user.c | 133
> >> ++++++++++++++++++++++++++++++----------------
> >> 2 files changed, 130 insertions(+), 47 deletions(-)
> >>
> >
> > Ping !
> > Michael, MarcAndre, Did you have a chance to look at this patch series?
> >
>
> That's not going to make it in 2.7 I am afraid.
It's a bugfix so - depends on how quickly can comments be addressed.
--
MST
next prev parent reply other threads:[~2016-07-27 4:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 6:34 [Qemu-devel] [PATCH v3 0/2] vhost-user: Extend protocol to receive replies on any command Prerna Saxena
2016-07-07 6:34 ` [Qemu-devel] [PATCH v3 1/2] vhost-user: Introduce a new protocol feature REPLY_ACK Prerna Saxena
2016-07-07 6:34 ` [Qemu-devel] [PATCH v3 2/2] vhost-user: Attempt to fix a race with set_mem_table Prerna Saxena
2016-07-25 6:41 ` [Qemu-devel] [PATCH v3 0/2] vhost-user: Extend protocol to receive replies on any command Prerna
2016-07-25 10:27 ` Marc-André Lureau
2016-07-25 10:34 ` Prerna Saxena
2016-07-27 4:21 ` Michael S. Tsirkin [this message]
2016-07-27 10:00 ` Prerna Saxena
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=20160727072039-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=anilkumar.boggarapu@nutanix.com \
--cc=felipe@nutanix.com \
--cc=marcandre.lureau@gmail.com \
--cc=prerna.saxena@nutanix.com \
--cc=qemu-devel@nongnu.org \
--cc=saxenap.ltc@gmail.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).