From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id D1F215A86 for ; Thu, 17 Dec 2015 12:57:22 +0100 (CET) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga102.jf.intel.com with ESMTP; 17 Dec 2015 03:57:20 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,440,1444719600"; d="scan'208,217";a="843181142" Received: from irsmsx106.ger.corp.intel.com ([163.33.3.31]) by orsmga001.jf.intel.com with ESMTP; 17 Dec 2015 03:57:20 -0800 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.23]) by IRSMSX106.ger.corp.intel.com ([169.254.8.228]) with mapi id 14.03.0248.002; Thu, 17 Dec 2015 11:57:18 +0000 From: "Czesnowicz, Przemyslaw" To: Abhijeet Karve Thread-Topic: [dpdk-dev] DPDK OVS on Ubuntu 14.04# Issue's Resolved# Successfully setup DPDK OVS with vhostuser Thread-Index: AQHRNv1clgh7VwIUg06xbzO92L7eNZ7MLcVAgAEuzQCAAbaI0A== Date: Thu, 17 Dec 2015 11:57:16 +0000 Message-ID: References: <745DB4B8861F8E4B9849C970520ABBF149834E55@ORSMSX102.amr.corp.intel.com> <738D45BC1F695740A983F43CFE1B7EA943921E56@IRSMSX108.ger.corp.intel.com> In-Reply-To: Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYWZiNDU4MTUtMmY3OC00YzFhLWIzMWItMmEyNjMyNGFiNDNlIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjQuMTAuMTkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiVFRKdWNLWE9aSTV5elZzNk1sY3g4S0tPdVRLbmFsTXRXQlVWaWw1MGRjZz0ifQ== x-ctpclassification: CTP_IC x-originating-ip: [163.33.239.182] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Cc: "dev@dpdk.org" , "discuss@openvswitch.org" Subject: Re: [dpdk-dev] DPDK OVS on Ubuntu 14.04# Issue's Resolved# Successfully setup DPDK OVS with vhostuser 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, 17 Dec 2015 11:57:24 -0000 HI Abhijeet, For Kilo you need to use ovsdpdk mechanism driver and a matching agent to i= ntegrate ovs-dpdk with OpenStack. The guide you are following only talks about running ovs-dpdk not how it sh= ould be integrated with OpenStack. Please follow this guide: https://github.com/openstack/networking-ovs-dpdk/blob/stable/kilo/doc/sourc= e/getstarted/ubuntu.rst Best regards Przemek From: Abhijeet Karve [mailto:abhijeet.karve@tcs.com] Sent: Wednesday, December 16, 2015 9:37 AM To: Czesnowicz, Przemyslaw Cc: dev@dpdk.org; discuss@openvswitch.org; Gray, Mark D Subject: RE: [dpdk-dev] DPDK OVS on Ubuntu 14.04# Issue's Resolved# Success= fully setup DPDK OVS with vhostuser Hi Przemek, We have configured the accelerated data path between a physical interface t= o the VM using openvswitch netdev-dpdk with vhost-user support. The VM crea= ted with this special data path and vhost library, I am calling as DPDK ins= tance. If assigning ip manually to the newly created Cirros VM instance, We are ab= le to make 2 VM's to communicate on the same compute node. Else it's not as= sociating any ip through DHCP though DHCP is in compute node only. Yes it's a compute + controller node setup and we are using following softw= are platform on compute node: _____________ Openstack: Kilo Distribution: Ubuntu 14.04 OVS Version: 2.4.0 DPDK 2.0.0 _____________ We are following the intel guide https://software.intel.com/en-us/blogs/201= 5/06/09/building-vhost-user-for-ovs-today-using-dpdk-200 When doing "ovs-vsctl show" in compute node, it shows below output: _____________________________________________ ovs-vsctl show c2ec29a5-992d-4875-8adc-1265c23e0304 Bridge br-ex Port phy-br-ex Interface phy-br-ex type: patch options: {peer=3Dint-br-ex} Port br-ex Interface br-ex type: internal Bridge br-tun fail_mode: secure Port br-tun Interface br-tun type: internal Port patch-int Interface patch-int type: patch options: {peer=3Dpatch-tun} Bridge br-int fail_mode: secure Port "qvo0ae19a43-b6" tag: 2 Interface "qvo0ae19a43-b6" Port br-int Interface br-int type: internal Port "qvo31c89856-a2" tag: 1 Interface "qvo31c89856-a2" Port patch-tun Interface patch-tun type: patch options: {peer=3Dpatch-int} Port int-br-ex Interface int-br-ex type: patch options: {peer=3Dphy-br-ex} Port "qvo97fef28a-ec" tag: 2 Interface "qvo97fef28a-ec" Bridge br-dpdk Port br-dpdk Interface br-dpdk type: internal Bridge "br0" Port "br0" Interface "br0" type: internal Port "dpdk0" Interface "dpdk0" type: dpdk Port "vhost-user-2" Interface "vhost-user-2" type: dpdkvhostuser Port "vhost-user-0" Interface "vhost-user-0" type: dpdkvhostuser Port "vhost-user-1" Interface "vhost-user-1" type: dpdkvhostuser ovs_version: "2.4.0" root@dpdk:~# _____________________________________________ Open flows output in bridge in compute node are as below: _____________________________________________ root@dpdk:~# ovs-ofctl dump-flows br-tun NXST_FLOW reply (xid=3D0x4): cookie=3D0x0, duration=3D71796.741s, table=3D0, n_packets=3D519, n_bytes= =3D33794, idle_age=3D19982, hard_age=3D65534, priority=3D1,in_port=3D1 acti= ons=3Dresubmit(,2) cookie=3D0x0, duration=3D71796.700s, table=3D0, n_packets=3D0, n_bytes=3D0= , idle_age=3D65534, hard_age=3D65534, priority=3D0 actions=3Ddrop cookie=3D0x0, duration=3D71796.649s, table=3D2, n_packets=3D0, n_bytes=3D0= , idle_age=3D65534, hard_age=3D65534, priority=3D0,dl_dst=3D00:00:00:00:00:= 00/01:00:00:00:00:00 actions=3Dresubmit(,20) cookie=3D0x0, duration=3D71796.610s, table=3D2, n_packets=3D519, n_bytes= =3D33794, idle_age=3D19982, hard_age=3D65534, priority=3D0,dl_dst=3D01:00:0= 0:00:00:00/01:00:00:00:00:00 actions=3Dresubmit(,22) cookie=3D0x0, duration=3D71794.631s, table=3D3, n_packets=3D0, n_bytes=3D0= , idle_age=3D65534, hard_age=3D65534, priority=3D1,tun_id=3D0x5c actions=3D= mod_vlan_vid:2,resubmit(,10) cookie=3D0x0, duration=3D71794.316s, table=3D3, n_packets=3D0, n_bytes=3D0= , idle_age=3D65534, hard_age=3D65534, priority=3D1,tun_id=3D0x57 actions=3D= mod_vlan_vid:1,resubmit(,10) cookie=3D0x0, duration=3D71796.565s, table=3D3, n_packets=3D0, n_bytes=3D0= , idle_age=3D65534, hard_age=3D65534, priority=3D0 actions=3Ddrop cookie=3D0x0, duration=3D71796.522s, table=3D4, n_packets=3D0, n_bytes=3D0= , idle_age=3D65534, hard_age=3D65534, priority=3D0 actions=3Ddrop cookie=3D0x0, duration=3D71796.481s, table=3D10, n_packets=3D0, n_bytes=3D= 0, idle_age=3D65534, hard_age=3D65534, priority=3D1 actions=3Dlearn(table= =3D20,hard_timeout=3D300,priority=3D1,NXM_OF_VLAN_TCI[0..11],NXM_OF_ETH_DST= []=3DNXM_OF_ETH_SRC[],load:0->NXM_OF_VLAN_TCI[],load:NXM_NX_TUN_ID[]->NXM_N= X_TUN_ID[],output:NXM_OF_IN_PORT[]),output:1 cookie=3D0x0, duration=3D71796.439s, table=3D20, n_packets=3D0, n_bytes=3D= 0, idle_age=3D65534, hard_age=3D65534, priority=3D0 actions=3Dresubmit(,22) cookie=3D0x0, duration=3D71796.398s, table=3D22, n_packets=3D519, n_bytes= =3D33794, idle_age=3D19982, hard_age=3D65534, priority=3D0 actions=3Ddrop root@dpdk:~# root@dpdk:~# root@dpdk:~# root@dpdk:~# ovs-ofctl dump-flows br-tun int NXST_FLOW reply (xid=3D0x4): cookie=3D0x0, duration=3D71801.275s, table=3D0, n_packets=3D0, n_bytes=3D0= , idle_age=3D65534, hard_age=3D65534, priority=3D2,in_port=3D10 actions=3Dd= rop cookie=3D0x0, duration=3D71801.862s, table=3D0, n_packets=3D661, n_bytes= =3D48912, idle_age=3D19981, hard_age=3D65534, priority=3D1 actions=3DNORMAL cookie=3D0x0, duration=3D71801.817s, table=3D23, n_packets=3D0, n_bytes=3D= 0, idle_age=3D65534, hard_age=3D65534, priority=3D0 actions=3Ddrop root@dpdk:~# _____________________________________________ Further we don't know what all the network changes(Packet Flow addition) if= required for associating IP address through the DHCP. Would be really appreciate if have clarity on DHCP flow establishment. Thanks & Regards Abhijeet Karve From: "Czesnowicz, Przemyslaw" > To: Abhijeet Karve >, "Gray, Mark D" = > Cc: "dev@dpdk.org" >, "discuss@openvswitch.org" > Date: 12/15/2015 09:13 PM Subject: RE: [dpdk-dev] DPDK OVS on Ubuntu 14.04# Issue's Resolved# = Successfully setup DPDK OVS with vhostuser ________________________________ Hi Abhijeet, If you answer below questions it will help me understand your problem. What do you mean by DPDK instance? Are you able to communicate with other VM's on the same compute node? Can you check if the DHCP requests arrive on the controller node? (I'm assu= ming this is at least compute+ controller setup) Best regards Przemek > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Abhijeet Karve > Sent: Tuesday, December 15, 2015 5:56 AM > To: Gray, Mark D > Cc: dev@dpdk.org; discuss@openvswitch.org > Subject: Re: [dpdk-dev] DPDK OVS on Ubuntu 14.04# Issue's Resolved# > Successfully setup DPDK OVS with vhostuser > > Dear All, > > After seting up system boot parameters as shown below, the issue is > resolved now & we are able to successfully setup openvswitch netdev-dpdk > with vhostuser support. > > __________________________________________________________ > _______________________________________________________ > Setup 2 sets of huge pages with different sizes. One for Vhost and anothe= r > for Guest VM. > Edit /etc/default/grub. > GRUB_CMDLINE_LINUX=3D"iommu=3Dpt intel_iommu=3Don hugepagesz= =3D1G > hugepages=3D10 hugepagesz=3D2M hugepages=3D4096" > # update-grub > - Mount the huge pages into different directory. > # sudo mount -t hugetlbfs nodev /mnt/huge_2M -o pagesize=3D2M > # sudo mount -t hugetlbfs nodev /mnt/huge_1G -o pagesize=3D1G > __________________________________________________________ > _______________________________________________________ > > At present we are facing an issue in Testing DPDK application on setup. I= n our > scenario, We have DPDK instance launched on top of the Openstack Kilo > compute node. Not able to assign DHCP IP from controller. > > > Thanks & Regards > Abhijeet Karve > > =3D=3D=3D=3D=3D-----=3D=3D=3D=3D=3D-----=3D=3D=3D=3D=3D > Notice: The information contained in this e-mail message and/or > attachments to it may contain confidential or privileged information. If = you > are not the intended recipient, any dissemination, use, review, distribut= ion, > printing or copying of the information contained in this e-mail message > and/or attachments to it are strictly prohibited. If you have received th= is > communication in error, please notify us by reply e-mail or telephone and > immediately and permanently delete the message and any attachments. > Thank you >