On Fri, Apr 28, 2017 at 09:57:20AM +0200, Maxime Coquelin wrote:
> >>>Maybe we could introduce a version message? With that, we could tell
> >>>whether the frontend has fixed the known bug or not.
> >>
> >>That's a possibility, but this is not really the role of a protocol
> >>version. As in this c
On 04/28/2017 09:35 AM, Yuanhan Liu wrote:
On Fri, Apr 28, 2017 at 09:23:54AM +0200, Maxime Coquelin wrote:
On 04/28/2017 04:25 AM, Yuanhan Liu wrote:
On Thu, Apr 27, 2017 at 10:52:20AM +0200, Maxime Coquelin wrote:
On 04/27/2017 10:20 AM, Yuanhan Liu wrote:
On Thu, Apr 27, 2017 at 09:5
On Fri, Apr 28, 2017 at 03:35:53PM +0800, Yuanhan Liu wrote:
> > >Maybe we could introduce a version message? With that, we could tell
> > >whether the frontend has fixed the known bug or not.
> >
> > That's a possibility, but this is not really the role of a protocol
> > version. As in this case,
On Fri, Apr 28, 2017 at 09:23:54AM +0200, Maxime Coquelin wrote:
>
>
> On 04/28/2017 04:25 AM, Yuanhan Liu wrote:
> >On Thu, Apr 27, 2017 at 10:52:20AM +0200, Maxime Coquelin wrote:
> >>
> >>
> >>On 04/27/2017 10:20 AM, Yuanhan Liu wrote:
> >>>On Thu, Apr 27, 2017 at 09:56:47AM +0200, Maxime Coqu
On 04/28/2017 04:25 AM, Yuanhan Liu wrote:
On Thu, Apr 27, 2017 at 10:52:20AM +0200, Maxime Coquelin wrote:
On 04/27/2017 10:20 AM, Yuanhan Liu wrote:
On Thu, Apr 27, 2017 at 09:56:47AM +0200, Maxime Coquelin wrote:
Hi Zhiyong,
+Marc-André
On 04/27/2017 08:34 AM, Zhiyong Yang wrote:
vho
On Thu, Apr 27, 2017 at 10:52:20AM +0200, Maxime Coquelin wrote:
>
>
> On 04/27/2017 10:20 AM, Yuanhan Liu wrote:
> >On Thu, Apr 27, 2017 at 09:56:47AM +0200, Maxime Coquelin wrote:
> >>Hi Zhiyong,
> >>
> >>+Marc-André
> >>
> >>On 04/27/2017 08:34 AM, Zhiyong Yang wrote:
> >>>vhost since dpdk17.0
On 04/27/2017 10:20 AM, Yuanhan Liu wrote:
On Thu, Apr 27, 2017 at 09:56:47AM +0200, Maxime Coquelin wrote:
Hi Zhiyong,
+Marc-André
On 04/27/2017 08:34 AM, Zhiyong Yang wrote:
vhost since dpdk17.02 + qemu2.7 and above will cause failures of
new connection when negotiating to set MQ. (one qu
On 04/27/2017 10:24 AM, Yang, Zhiyong wrote:
Hi, Maxime:
-Original Message-
From: Maxime Coquelin [mailto:maxime.coque...@redhat.com]
Sent: Thursday, April 27, 2017 4:05 PM
To: Yang, Zhiyong ; dev@dpdk.org
Cc: yuanhan@linux.intel.com; Loftus, Ciara ; Marc-
André Lureau
Subject: R
Hi, yuanhan:
> -Original Message-
> From: Yuanhan Liu [mailto:yuanhan@linux.intel.com]
> Sent: Thursday, April 27, 2017 4:12 PM
> To: Yang, Zhiyong
> Cc: dev@dpdk.org; maxime.coque...@redhat.com; Loftus, Ciara
>
> Subject: Re: [PATCH] vhost: fix MQ fails to startup
>
> On Thu, Apr 2
On Thu, Apr 27, 2017 at 09:56:47AM +0200, Maxime Coquelin wrote:
> Hi Zhiyong,
>
> +Marc-André
>
> On 04/27/2017 08:34 AM, Zhiyong Yang wrote:
> >vhost since dpdk17.02 + qemu2.7 and above will cause failures of
> >new connection when negotiating to set MQ. (one queue pair works
> >well).Because t
Hi, Maxime:
> -Original Message-
> From: Maxime Coquelin [mailto:maxime.coque...@redhat.com]
> Sent: Thursday, April 27, 2017 4:05 PM
> To: Yang, Zhiyong ; dev@dpdk.org
> Cc: yuanhan@linux.intel.com; Loftus, Ciara ; Marc-
> André Lureau
> Subject: Re: [PATCH] vhost: fix MQ fails to st
On Thu, Apr 27, 2017 at 02:34:53PM +0800, Zhiyong Yang wrote:
> vhost since dpdk17.02 + qemu2.7 and above will cause failures of
> new connection when negotiating to set MQ. (one queue pair works
> well).Because there exist some bugs in qemu code when introducing
> VHOST_USER_PROTOCOL_F_REPLY_ACK t
On 04/27/2017 09:56 AM, Maxime Coquelin wrote:
Hi Zhiyong,
+Marc-André
On 04/27/2017 08:34 AM, Zhiyong Yang wrote:
vhost since dpdk17.02 + qemu2.7 and above will cause failures of
new connection when negotiating to set MQ. (one queue pair works
well).Because there exist some bugs in qemu cod
Hi Zhiyong,
+Marc-André
On 04/27/2017 08:34 AM, Zhiyong Yang wrote:
vhost since dpdk17.02 + qemu2.7 and above will cause failures of
new connection when negotiating to set MQ. (one queue pair works
well).Because there exist some bugs in qemu code when introducing
VHOST_USER_PROTOCOL_F_REPLY_ACK
>
> vhost since dpdk17.02 + qemu2.7 and above will cause failures of
> new connection when negotiating to set MQ. (one queue pair works
> well).Because there exist some bugs in qemu code when introducing
> VHOST_USER_PROTOCOL_F_REPLY_ACK to qemu. when dealing with the
> vhost
> message VHOST_USER_
vhost since dpdk17.02 + qemu2.7 and above will cause failures of
new connection when negotiating to set MQ. (one queue pair works
well).Because there exist some bugs in qemu code when introducing
VHOST_USER_PROTOCOL_F_REPLY_ACK to qemu. when dealing with the vhost
message VHOST_USER_SET_MEM_TABLE f
16 matches
Mail list logo
