From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from jaguar.aricent.com (jaguar.aricent.com [180.151.2.24]) by dpdk.org (Postfix) with ESMTP id 7860D58EB for ; Thu, 30 Jan 2014 11:15:04 +0100 (CET) Received: from jaguar.aricent.com (localhost [127.0.0.1]) by postfix.imss71 (Postfix) with ESMTP id D03BC36B3C; Thu, 30 Jan 2014 15:46:03 +0530 (IST) Received: from GUREXHT01.ASIAN.AD.ARICENT.COM (gurexht01.asian.ad.aricent.com [10.203.171.136]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by jaguar.aricent.com (Postfix) with ESMTP id B971636B29; Thu, 30 Jan 2014 15:46:03 +0530 (IST) Received: from GUREXMB01.asian.ad.aricent.com ([10.203.171.134]) by GUREXHT01.ASIAN.AD.ARICENT.COM ([10.203.171.136]) with mapi; Thu, 30 Jan 2014 15:46:04 +0530 From: Prashant Upadhyaya To: Pravin Shelar Date: Thu, 30 Jan 2014 15:45:59 +0530 Thread-Topic: [dpdk-dev] [PATCH RFC] dpif-netdev: Add support Intel DPDK based ports. Thread-Index: Ac8dOTpTfuBzlz4WRbiKxy0dWMtXZwAarJ9w Message-ID: References: <1390873715-26714-1-git-send-email-pshelar@nicira.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-TM-AS-MML: No Cc: "dev@openvswitch.org" , "dev@dpdk.org" , Gerald Rogers , "dpdk-ovs@lists.01.org" Subject: Re: [dpdk-dev] [PATCH RFC] dpif-netdev: Add support Intel DPDK based ports. 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, 30 Jan 2014 10:15:04 -0000 Hi Pravin, Request you to please validate atleast one method to interface VM's with yo= ur innovative dpdk port on the OVS. Preferably IVSHM. Please do publish the steps for that too. We really need the above for huge acceptance. Regards -Prashant -----Original Message----- From: Pravin Shelar [mailto:pshelar@nicira.com] Sent: Thursday, January 30, 2014 3:00 AM To: Prashant Upadhyaya Cc: dev@openvswitch.org; dev@dpdk.org; dpdk-ovs@lists.01.org; Gerald Rogers Subject: Re: [dpdk-dev] [PATCH RFC] dpif-netdev: Add support Intel DPDK bas= ed ports. On Wed, Jan 29, 2014 at 12:56 AM, Prashant Upadhyaya wrote: > Hi Pravin, > > I think your stuff is on the brink of a creating a mini revolution :) > > Some questions inline below -- > + ovs-vsctl add-port br0 dpdk0 -- set Interface dpdk0 type=3Ddpdk > What do you mean by portid here, do you mean the physical interface id li= ke eth0 which I have bound to igb_uio now ? > If I have multiple interfaces I have assigned igb_uio to, eg. eth0, eth1,= eth2 etc., what is the id mapping for those ? > Port id is id assigned by DPDK. DPDK interface takes this port id as argume= nt. Currently you need to look at pci id to figure out the device mapping t= o port id. I know it is clean and I am exploring better interface so that w= e can specify device names to ovs-vsctl. > If I have VM's running, then typically how to interface those VM's to thi= s OVS in user space now, do I use the same classical 'tap' interface and ad= d it to the OVS above. tap device will work, but you would not get performance primarily due to sc= heduling delay and memcopy. DPDK has multiple drivers to create interface with KVM guests OS. those should perform better. I have no tried it yet. > What is the actual path the data takes from the VM now all the way to the= switch, wouldn't it be hypervisor to kernel to OVS switch in user space to= other VM/Network ? Depends on method you use. e.g. Memnic bypass hypervisor and host kernel en= tirely. > I think if we can solve the VM to OVS port connectivity remaining in user= space only, then we have a great thing at our hand. Kindly comment on this. > right, performance looks pretty good. Still DPDK needs constant polling whi= ch consumes more power. RFC ovs-dkdp patch has simple polling which need tw= eaking for better power usage. Thanks, Pravin. > Regards > -Prashant > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D Please refer to http://www.aricent.com/legal/email_disclaimer.html for important disclosures regarding this electronic communication. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D