On Mon, Jul 04, 2016 at 04:50:04PM +, Prerna Saxena wrote:
> Hi Michael,
> Thank you for taking a look.
>
>
>
>
>
> On 04/07/16 5:29 pm, "Michael S. Tsirkin" wrote:
>
> >On Fri, Jul 01, 2016 at 02:46:20AM -0700, Prerna Saxena wrote:
> >> From: Prerna Saxena
> >>
> >> The current vhost-
Hi Michael,
Thank you for taking a look.
On 04/07/16 5:29 pm, "Michael S. Tsirkin" wrote:
>On Fri, Jul 01, 2016 at 02:46:20AM -0700, Prerna Saxena wrote:
>> From: Prerna Saxena
>>
>> The current vhost-user protocol requires the client to send responses to
>> only a
>> few commands. For th
On Fri, Jul 01, 2016 at 02:46:20AM -0700, Prerna Saxena wrote:
> From: Prerna Saxena
>
> 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 -- i
Hi Marc-Andre,
Thank you for taking a look.
On 03/07/16 5:17 pm, "Marc-André Lureau" wrote:
>Hi
>
>On Fri, Jul 1, 2016 at 11:46 AM, Prerna Saxena wrote:
>> From: Prerna Saxena
>>
>> The current vhost-user protocol requires the client to send responses to
>> only a
>> few commands. For the
Hi
On Fri, Jul 1, 2016 at 11:46 AM, Prerna Saxena wrote:
> From: Prerna Saxena
>
> 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, di
From: Prerna Saxena
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 lea
