From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <avi.cohen@huawei.com>
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [45.249.212.187])
 by dpdk.org (Postfix) with ESMTP id F196A271
 for <users@dpdk.org>; Wed, 28 Jun 2017 08:45:38 +0200 (CEST)
Received: from 172.30.72.53 (EHLO nkgeml411-hub.china.huawei.com)
 ([172.30.72.53])
 by dggrg01-dlp.huawei.com (MOS 4.4.6-GA FastPath queued)
 with ESMTP id ARC00016; Wed, 28 Jun 2017 14:45:34 +0800 (CST)
Received: from FRAEML703-CAH.china.huawei.com (10.206.14.34) by
 nkgeml411-hub.china.huawei.com (10.98.56.70) with Microsoft SMTP Server (TLS)
 id 14.3.235.1; Wed, 28 Jun 2017 14:45:33 +0800
Received: from FRAEML521-MBX.china.huawei.com ([169.254.1.122]) by
 fraeml703-cah.china.huawei.com ([10.206.14.34]) with mapi id 14.03.0301.000;
 Wed, 28 Jun 2017 08:45:29 +0200
From: "Avi Cohen (A)" <avi.cohen@huawei.com>
To: "Tan, Jianfeng" <jianfeng.tan@intel.com>, "dpdk-ovs@lists.01.org"
 <dpdk-ovs@lists.01.org>, "users@dpdk.org" <users@dpdk.org>
Thread-Topic: VIRTIO for containers
Thread-Index: AQHS71DYC699Y73ftUG6MPPfZcA7c6I503Qg
Date: Wed, 28 Jun 2017 06:45:28 +0000
Message-ID: <B84047ECBD981D4B93EAE5A6245AA361013C9047@FRAEML521-MBX.china.huawei.com>
References: <B84047ECBD981D4B93EAE5A6245AA361013C5A45@FRAEML521-MBS.china.huawei.com>
 <ED26CBA2FAD1BF48A8719AEF02201E3651217C51@SHSMSX103.ccr.corp.intel.com>
 <B84047ECBD981D4B93EAE5A6245AA361013C7D2B@FRAEML521-MBX.china.huawei.com>
 <ED26CBA2FAD1BF48A8719AEF02201E36512186DE@SHSMSX103.ccr.corp.intel.com>
 <B84047ECBD981D4B93EAE5A6245AA361013C8E03@FRAEML521-MBX.china.huawei.com>
 <e93928ec-8e44-dda5-c07a-9118b5ff7f14@intel.com>
In-Reply-To: <e93928ec-8e44-dda5-c07a-9118b5ff7f14@intel.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.200.202.183]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0),
 refid=str=0001.0A090204.5953508F.003D, ss=1, re=0.000, recu=0.000, reip=0.000,
 cl=1, cld=1, fgs=0, ip=169.254.1.122,
 so=2014-11-16 11:51:01, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 93d260bafaaa425b015814967d13f80b
Subject: Re: [dpdk-users] VIRTIO for containers
X-BeenThere: users@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK usage discussions <users.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/users>,
 <mailto:users-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/users/>
List-Post: <mailto:users@dpdk.org>
List-Help: <mailto:users-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/users>,
 <mailto:users-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jun 2017 06:45:42 -0000

Thank you Jianfeng

> -----Original Message-----
> From: Tan, Jianfeng [mailto:jianfeng.tan@intel.com]
> Sent: Tuesday, 27 June, 2017 5:22 PM
> To: Avi Cohen (A); dpdk-ovs@lists.01.org; users@dpdk.org
> Subject: Re: VIRTIO for containers
>=20
>=20
>=20
> On 6/26/2017 8:06 PM, Avi Cohen (A) wrote:
> > Thank You Jianfeng
> >
> >> We have developed virtio-user + vhost-kernel as the backend. In that
> >> scenario, you can add the tap interface into a container network
> namespace.
> >> And there's a vhost kthread to push the data out to user space.
> >>
> >> And I cannot guarantee the performance as it has diametric model in
> >> VM
> >> (virtio) - OVS-DPDK (vhost).
> >>
> > [Avi Cohen (A)]
> > Can you refer to a document how to run this setup?
>=20
> Please refer to
> http://dpdk.org/doc/guides/howto/virtio_user_as_exceptional_path.html
>=20
[Avi Cohen (A)]=20
My setup includes a container and ovs-dpdk , i still not sure about:
 - How to set the virtio backend port in the ovs-dpdk ?
 - How to set the container with the virtio frontend ?
Best Regards
avi

> Thanks,
> Jianfeng
>=20
> > Best Regards
> > avi
> >>> I've tested the performance of a container connected to OVS-DPDK
> >>> via vdev-af_packet  and processed by virtual PMD, and its
> >>> performance is good [uses mmap'ed to userspace  - zero copy RX/TX
> >>> ring buffer] but not good as  the performance  of a  VM connected
> >>> to OVS-DPDK (@host) via vhost-user virtio.
> >>> Best Regards
> >>> avi
> >>>
> >>>> -----Original Message-----
> >>>> From: Tan, Jianfeng [mailto:jianfeng.tan@intel.com]
> >>>> Sent: Monday, 26 June, 2017 6:15 AM
> >>>> To: Avi Cohen (A); dpdk-ovs@lists.01.org; users@dpdk.org
> >>>> Subject: RE: VIRTIO for containers
> >>>>
> >>>> Hi Avi,
> >>>>
> >>>>> -----Original Message-----
> >>>>> From: users [mailto:users-bounces@dpdk.org] On Behalf Of Avi Cohen
> >>>>> (A)
> >>>>> Sent: Sunday, June 25, 2017 11:13 PM
> >>>>> To: dpdk-ovs@lists.01.org; users@dpdk.org
> >>>>> Subject: [dpdk-users] VIRTIO for containers
> >>>>>
> >>>>> Hello,
> >>>>> Does  anyone know the status of this project
> >>>>> http://dpdk.org/ml/archives/dev/2015-November/027732.html  -
> >>>>> Implementing a virtio device for containers ?
> >>>> It has been upstreamed since v16.07. Here is a howto doc:
> >>>>
> >>>
> http://dpdk.org/doc/guides/howto/virtio_user_for_container_networking.
> >>> h
> >>>> tml
> >>>>
> >>>>
> >>>> Thanks,
> >>>> Jianfeng
> >>>>
> >>>>> Best Regards
> >>>>> avi