On Mon, Dec 12, 2016 at 06:54:00PM +0100, Maxime Coquelin wrote:
> REPLY_ACK features provide a generic way for QEMU to ensure both
> completion and success of a request.
>
> As described in vhost-user spec in QEMU repository, QEMU sets
> VHOST_USER_NEED_REPLY flag (bit 3) when expecting a reply_a
On 12/13/2016 11:03 AM, Yuanhan Liu wrote:
On Tue, Dec 13, 2016 at 10:57:10AM +0100, Maxime Coquelin wrote:
On 12/13/2016 10:56 AM, Yuanhan Liu wrote:
On Mon, Dec 12, 2016 at 06:54:00PM +0100, Maxime Coquelin wrote:
REPLY_ACK features provide a generic way for QEMU to ensure both
completio
On Tue, Dec 13, 2016 at 10:57:10AM +0100, Maxime Coquelin wrote:
>
>
> On 12/13/2016 10:56 AM, Yuanhan Liu wrote:
> >On Mon, Dec 12, 2016 at 06:54:00PM +0100, Maxime Coquelin wrote:
> >>REPLY_ACK features provide a generic way for QEMU to ensure both
> >>completion and success of a request.
> >>
On 12/13/2016 10:56 AM, Yuanhan Liu wrote:
On Mon, Dec 12, 2016 at 06:54:00PM +0100, Maxime Coquelin wrote:
REPLY_ACK features provide a generic way for QEMU to ensure both
completion and success of a request.
As described in vhost-user spec in QEMU repository, QEMU sets
VHOST_USER_NEED_REPLY
On Mon, Dec 12, 2016 at 06:54:00PM +0100, Maxime Coquelin wrote:
> REPLY_ACK features provide a generic way for QEMU to ensure both
> completion and success of a request.
>
> As described in vhost-user spec in QEMU repository, QEMU sets
> VHOST_USER_NEED_REPLY flag (bit 3) when expecting a reply_a
5 matches
Mail list logo