On Fri, Sep 09, 2016 at 02:24:20PM +0800, Tan, Jianfeng wrote:
>
>
> On 9/9/2016 2:03 PM, Yuanhan Liu wrote:
> >>GET_PROTOCOL_FEATURES
> >>is not supported yet. I see those features in PROTOCOL_FEATURES is for live
> >>migration (right?).
> >Not exactly. PROTOCOL_FEATURES was firstly introduced w
On 9/9/2016 2:03 PM, Yuanhan Liu wrote:
>> GET_PROTOCOL_FEATURES
>> is not supported yet. I see those features in PROTOCOL_FEATURES is for live
>> migration (right?).
> Not exactly. PROTOCOL_FEATURES was firstly introduced while MQ was
> enabled. Thus it's no wonder MQ is the first protocol featu
On Fri, Sep 09, 2016 at 01:50:16PM +0800, Tan, Jianfeng wrote:
> On 9/9/2016 12:19 PM, Yuanhan Liu wrote:
>
> >>
> >>
> >> Never mind, above fix on the vhost side will not take effect on
> >> existing
> >> vpp-vhost implementations.
> >>
> >> Actually, I was talking about the
On 9/9/2016 12:19 PM, Yuanhan Liu wrote:
>>
>>
>> Never mind, above fix on the vhost side will not take effect on
>> existing
>> vpp-vhost implementations.
>>
>> Actually, I was talking about the DPDK vhost implementation :)
>>
>>
>> This patch is talking about vpp's native
On Fri, Sep 09, 2016 at 11:59:18AM +0800, Tan, Jianfeng wrote:
> It's actually a good catch. After a light thought, I think in
> DPDK vhost, we
> may need to create those virtqueues once unix socket gets
> connected, just
> like in vhost-net, virtqu
On 9/8/2016 8:18 PM, Yuanhan Liu wrote:
> On Thu, Sep 08, 2016 at 04:53:22PM +0800, Tan, Jianfeng wrote:
>>
>> On 9/6/2016 4:20 PM, Yuanhan Liu wrote:
>>> On Tue, Sep 06, 2016 at 03:54:30PM +0800, Tan, Jianfeng wrote:
Hi Yuanhan,
On 9/6/2016 2:42 PM, Yuanhan Liu wrote:
> O
On Thu, Sep 08, 2016 at 04:53:22PM +0800, Tan, Jianfeng wrote:
>
>
> On 9/6/2016 4:20 PM, Yuanhan Liu wrote:
> >On Tue, Sep 06, 2016 at 03:54:30PM +0800, Tan, Jianfeng wrote:
> >>Hi Yuanhan,
> >>
> >>
> >>On 9/6/2016 2:42 PM, Yuanhan Liu wrote:
> >>>On Fri, Aug 05, 2016 at 11:36:42AM +, Jianf
On 9/6/2016 4:20 PM, Yuanhan Liu wrote:
> On Tue, Sep 06, 2016 at 03:54:30PM +0800, Tan, Jianfeng wrote:
>> Hi Yuanhan,
>>
>>
>> On 9/6/2016 2:42 PM, Yuanhan Liu wrote:
>>> On Fri, Aug 05, 2016 at 11:36:42AM +, Jianfeng Tan wrote:
When virtio_user is used with VPP's native vhost user, it
On Tue, Sep 06, 2016 at 03:54:30PM +0800, Tan, Jianfeng wrote:
> Hi Yuanhan,
>
>
> On 9/6/2016 2:42 PM, Yuanhan Liu wrote:
> >On Fri, Aug 05, 2016 at 11:36:42AM +, Jianfeng Tan wrote:
> >>When virtio_user is used with VPP's native vhost user, it cannot
> >>send/receive any packets.
> >>
> >>T
Hi Yuanhan,
On 9/6/2016 2:42 PM, Yuanhan Liu wrote:
> On Fri, Aug 05, 2016 at 11:36:42AM +, Jianfeng Tan wrote:
>> When virtio_user is used with VPP's native vhost user, it cannot
>> send/receive any packets.
>>
>> The root cause is that vpp-vhost-user translates the message
>> VHOST_USER_SET
On Fri, Aug 05, 2016 at 11:36:42AM +, Jianfeng Tan wrote:
> When virtio_user is used with VPP's native vhost user, it cannot
> send/receive any packets.
>
> The root cause is that vpp-vhost-user translates the message
> VHOST_USER_SET_FEATURES as puting this device into init state,
> aka, zero
[dpdk-dev] [PATCH 2/3] net/virtio_user: fix wrong sequence of
> messages
>
> On Fri, 5 Aug 2016 11:36:42 +
> Jianfeng Tan wrote:
>
> > When virtio_user is used with VPP's native vhost user, it cannot
> > send/receive any packets.
> >
>
When virtio_user is used with VPP's native vhost user, it cannot
send/receive any packets.
The root cause is that vpp-vhost-user translates the message
VHOST_USER_SET_FEATURES as puting this device into init state,
aka, zero all related structures. However, previous code
puts this message at last
On Fri, 5 Aug 2016 11:36:42 +
Jianfeng Tan wrote:
> When virtio_user is used with VPP's native vhost user, it cannot
> send/receive any packets.
>
> The root cause is that vpp-vhost-user translates the message
> VHOST_USER_SET_FEATURES as puting this device into init state,
> aka, zero all
14 matches
Mail list logo
