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 B20E8374E
 for <users@dpdk.org>; Tue, 23 May 2017 17:16:27 +0200 (CEST)
Received: from 172.30.72.57 (EHLO NKGEML413-HUB.china.huawei.com)
 ([172.30.72.57])
 by dggrg01-dlp.huawei.com (MOS 4.4.6-GA FastPath queued)
 with ESMTP id APC05988; Tue, 23 May 2017 23:16:23 +0800 (CST)
Received: from FRAEML704-CAH.china.huawei.com (10.206.14.35) by
 NKGEML413-HUB.china.huawei.com (10.98.56.74) with Microsoft SMTP Server (TLS)
 id 14.3.235.1; Tue, 23 May 2017 23:16:23 +0800
Received: from FRAEML521-MBX.china.huawei.com ([169.254.1.104]) by
 FRAEML704-CAH.china.huawei.com ([10.206.14.35]) with mapi id 14.03.0301.000;
 Tue, 23 May 2017 17:16:16 +0200
From: "Avi Cohen (A)" <avi.cohen@huawei.com>
To: "users@dpdk.org" <users@dpdk.org>
Thread-Topic: VHOST-USER  interface between ovs-dpdk and a VM
Thread-Index: AdLTyEZrVaNwY7t6QW66VwwfAC0bSQADzZgQ
Date: Tue, 23 May 2017 15:16:16 +0000
Message-ID: <B84047ECBD981D4B93EAE5A6245AA361013BCB38@FRAEML521-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.200.202.128]
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.0A020204.59245247.0396, ss=1, re=0.000, recu=0.000, reip=0.000,
 cl=1, cld=1, fgs=0, ip=169.254.1.104,
 so=2014-11-16 11:51:01, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 1ab3119f8b65df7f9f3ca82ac5ae3cad
Subject: Re: [dpdk-users] VHOST-USER  interface between ovs-dpdk and a VM
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: Tue, 23 May 2017 15:16:30 -0000

Sorry - step 4 below is incorrect:
There is a copy between guest OS and guest user-space.
Now the question is - what is the different of # of copies (copies of packe=
t from host to guest application) between this setup (OVS-DPDK) and setup w=
ith standard OVS (no dpdk)
Best regards

> -----Original Message-----
> From: Avi Cohen (A)
> Sent: Tuesday, 23 May, 2017 4:27 PM
> To: users@dpdk.org
> Subject: VHOST-USER interface between ovs-dpdk and a VM
>=20
> Hi,
> I'm trying to understand the packet life-cycle in   ovs-dpdk  (running on=
 host)
> communicating with  a VM through vhost-user interface:
> 1. packet is received via physical port to the device.
> 2.DMA  transfer   to mempools on huge-pages  allocated by dpdk-ovs - in  =
user-
> space.
> 3. ovs-dpdk copies this packet to the shared-vring of the associated  gue=
st
> (shared between ovs-dpdk userspace process and guest)=20
[Avi Cohen (A)]=20
4. no more copies in
> the guest - i.e. when any application running on the guest wants to consu=
me the
> packet - there is a zero copy between the shared-vring and the guest
> application.
>=20
> Is that correct ? how 4  is implemented ?  this is a communication betwee=
n OS
> in guest and application in guest . so how this is implemented with zero =
copy ?
>=20
> Best Regards
> avi