From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <avi.cohen@huawei.com>
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [45.249.212.189])
 by dpdk.org (Postfix) with ESMTP id 56B343DC
 for <users@dpdk.org>; Mon, 26 Jun 2017 08:17:00 +0200 (CEST)
Received: from 172.30.72.53 (EHLO nkgeml414-hub.china.huawei.com)
 ([172.30.72.53])
 by dggrg03-dlp.huawei.com (MOS 4.4.6-GA FastPath queued)
 with ESMTP id AQA89649; Mon, 26 Jun 2017 14:16:58 +0800 (CST)
Received: from FRAEML701-CAH.china.huawei.com (10.206.14.32) by
 nkgeml414-hub.china.huawei.com (10.98.56.75) with Microsoft SMTP Server (TLS)
 id 14.3.235.1; Mon, 26 Jun 2017 14:16:57 +0800
Received: from FRAEML521-MBX.china.huawei.com ([169.254.1.122]) by
 FRAEML701-CAH.china.huawei.com ([10.206.14.32]) with mapi id 14.03.0301.000;
 Mon, 26 Jun 2017 08:16:49 +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: AdLtxRmmOlpUk2OnQW+mTRMij+wCRQAZP+zgAAX4DJA=
Date: Mon, 26 Jun 2017 06:16:49 +0000
Message-ID: <B84047ECBD981D4B93EAE5A6245AA361013C7D2B@FRAEML521-MBX.china.huawei.com>
References: <B84047ECBD981D4B93EAE5A6245AA361013C5A45@FRAEML521-MBS.china.huawei.com>
 <ED26CBA2FAD1BF48A8719AEF02201E3651217C51@SHSMSX103.ccr.corp.intel.com>
In-Reply-To: <ED26CBA2FAD1BF48A8719AEF02201E3651217C51@SHSMSX103.ccr.corp.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.0A0B0206.5950A6DA.013B, 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: d4033bdb09b9e1f1e5f1c4908ab61498
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: Mon, 26 Jun 2017 06:17:03 -0000

Thanks Jianfeng,
For containers that are *not running*  DPDK  -  are there any thoughts to d=
evelop a 'virtio like' device? , for example to connect the container to OV=
S-DPDK ?=20
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) v=
ia 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
>=20
> Hi Avi,
>=20
> > -----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 ?
>=20
> 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
>=20
>=20
> Thanks,
> Jianfeng
>=20
> >
> > Best Regards
> > avi