From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 55A245A38 for ; Thu, 20 Aug 2015 10:37:41 +0200 (CEST) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga103.fm.intel.com with ESMTP; 20 Aug 2015 01:37:40 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.15,714,1432623600"; d="scan'208";a="772289968" Received: from pgsmsx104.gar.corp.intel.com ([10.221.44.91]) by fmsmga001.fm.intel.com with ESMTP; 20 Aug 2015 01:37:38 -0700 Received: from shsmsx103.ccr.corp.intel.com (10.239.4.69) by PGSMSX104.gar.corp.intel.com (10.221.44.91) with Microsoft SMTP Server (TLS) id 14.3.224.2; Thu, 20 Aug 2015 16:36:55 +0800 Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.171]) by SHSMSX103.ccr.corp.intel.com ([169.254.4.248]) with mapi id 14.03.0224.002; Thu, 20 Aug 2015 16:36:33 +0800 From: "Xie, Huawei" To: Zhuangyanying , "dev@dpdk.org" Thread-Topic: [RFC] combining dpdk with ovs via vhost_net Thread-Index: AdDbHMzt1z/8DYNUSWGAT+2WrdP2MQABZtkg Date: Thu, 20 Aug 2015 08:36:32 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: gaoxiaoqiu , "Zhangbo \(Oscar\)" , Zhbzg , Guohongzhen , Zhoujingbin Subject: Re: [dpdk-dev] [RFC] combining dpdk with ovs via vhost_net X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Aug 2015 08:37:41 -0000 Hi Yanping: I don't quite get your idea. Last year I had a design and POC which enables= user space virtio interface in container. Don't know if it has similarity with your proposal. Would post the idea lat= er in the following mail. > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Zhuangyanying > Sent: Thursday, August 20, 2015 3:50 PM > To: dev@dpdk.org > Cc: gaoxiaoqiu; Zhangbo (Oscar); Zhbzg; Guohongzhen; Zhoujingbin > Subject: [dpdk-dev] [RFC] combining dpdk with ovs via vhost_net >=20 > Hi all: > AFAIK, nowadays there's only one solution to apply DPDK into Docker > Containers, which is Passing-Through physical NIC to applications. > I'm now working on another solution, considering combining DPDK and > OVS via vhost-net, I name it "vhost_net pmd driver". > The detailed solution is as follows: > 1 Similar to the process of qemu<->vhost_net, we use a serial of ioctl > commands to make virtqueue visible to both vhost_net and vhost_net pmd > driver. > 2 In kvm guests, the tx/rx queue is consisted of GPA addresses, and th= e > vhost_net will transform it into HVA addresses, then the tap device could > copy datagram afterwards. However, GPA addresses are not necessary for > containers to fulfill the tx/rx queue. Thus, we fake it to fulfill the HV= A > addresses into the tx/rx queues, and pass the (HVA, HVA) map table to > vhost_net by VHOST_SET_MEM_TABLE ioctl during initialization. Thus *the > vhost_net codes could keep untouched*. > 3 the packet-transceiver-process is totally the same to virtio pmd dri= ver. >=20 > The demo has been worked out already. In the demo, the dpdk could > directly access vhost_net to realize L2 forward. > clients | host | contrain= er > ping | | > vm0 ----- > |ixgbe:enp131s0f0 <-> ovs:br0 <-> vhost:tap0 |<-> vhost-ne= t > pmd > | | | > | | testpm= d > | | | > vm1 <------ |ixgbe:enp131s0f1 <-> ovs:br1 <-> vhost:tap1 |<-> vhost-ne= t > pmd > | | >=20 > I don't know wheter this solution is acceptable here. Any blueprints= for > combining container with dpdk? any suggestions or advices? Thanks in > advance. >=20 >=20 > --- > Ann