From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <prashant.upadhyaya@aricent.com> Received: from jaguar.aricent.com (jaguar.aricent.com [180.151.2.24]) by dpdk.org (Postfix) with ESMTP id 3A87C594D for <dev@dpdk.org>; Wed, 5 Mar 2014 16:29:32 +0100 (CET) Received: from jaguar.aricent.com (localhost [127.0.0.1]) by postfix.imss71 (Postfix) with ESMTP id ED0C436B85; Wed, 5 Mar 2014 21:00:39 +0530 (IST) Received: from GUREXHT02.ASIAN.AD.ARICENT.COM (gurexht02.asian.ad.aricent.com [10.203.171.138]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by jaguar.aricent.com (Postfix) with ESMTP id E0DA236B37; Wed, 5 Mar 2014 21:00:39 +0530 (IST) Received: from GUREXMB01.asian.ad.aricent.com ([10.203.171.134]) by GUREXHT02.ASIAN.AD.ARICENT.COM ([10.203.171.138]) with mapi; Wed, 5 Mar 2014 21:00:40 +0530 From: Prashant Upadhyaya <prashant.upadhyaya@aricent.com> To: David Marchand <david.marchand@6wind.com> Date: Wed, 5 Mar 2014 21:00:38 +0530 Thread-Topic: [dpdk-dev] Which vmxnet3 pmd is to be used in dpdk 1.6.x? Thread-Index: Ac84hRKqJdz8OskxRhCddfO8cyX1MwAAfR0g Message-ID: <C7CE7EEF248E2B48BBA63D0ABEEE700C5A2A5060A9@GUREXMB01.ASIAN.AD.ARICENT.COM> References: <CAEbeQ+q2qZkufmZrHXd2r_JTq2wL-0=xm5-9ngqfqPqq8_A0eQ@mail.gmail.com> <C7CE7EEF248E2B48BBA63D0ABEEE700C5A2A50609C@GUREXMB01.ASIAN.AD.ARICENT.COM> <CALwxeUsV7NCgQBbL2XCSYm_RLx1tt5pMN_thbxnP_2D3ho4thw@mail.gmail.com> In-Reply-To: <CALwxeUsV7NCgQBbL2XCSYm_RLx1tt5pMN_thbxnP_2D3ho4thw@mail.gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-TM-AS-MML: No 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" <dev@dpdk.org> Subject: Re: [dpdk-dev] Which vmxnet3 pmd is to be used in dpdk 1.6.x? X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK <dev.dpdk.org> List-Unsubscribe: <http://dpdk.org/ml/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <http://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Wed, 05 Mar 2014 15:29:33 -0000 Hi David, The compilation error with debug flags on was that the functions -- vmxnet3= _txq_dump, vmxnet3_rxq_dump - are defined but not used. Not a serious error, I will try to get rid of the compiler flag which gener= ates this. However, I must reiterate, I _did_ bind my vmxnet3 device with igb_uio (and= I did not use any .so, because I was intending to use the builtin vmxnet3 = driver of dpdk 1.6.0r1), the bind succeeded, but then when I started the ap= plication, the dev init for vmxnet3 gave a core dump. Your patch and solution seems to be suggesting the reverse, i.e. when I don= 't bind with igb_uio but try to use the native driver. So please do try the= above combination as well. Regards -Prashant From: David Marchand [mailto:david.marchand@6wind.com] Sent: Wednesday, March 05, 2014 8:41 PM To: Prashant Upadhyaya Cc: Srinivasan J; dev@dpdk.org Subject: Re: [dpdk-dev] Which vmxnet3 pmd is to be used in dpdk 1.6.x? Hello Prashant, On Wed, Mar 5, 2014 at 3:28 PM, Prashant Upadhyaya <prashant.upadhyaya@aric= ent.com<mailto:prashant.upadhyaya@aricent.com>> wrote: Hi, I am also keen to know the answer to the question posted by Srini. The real question is -- is dpdk1.6.0r1 self-sufficient so that I don't need= any extensions etc., or do I still need something from outside like the us= ermap kernel driver etc. Secondly, if I turn on all the debug options for the vmxnet3 pmd in the con= fig file, 1.6.0r1 compilation runs into a problem and reports a function wh= ich is defined but not used. Can you send your build error ? (maybe in a separate thread ?) I am trying to bring up DPDK inside Fedora18 Guest on ESXi -- when I used D= PDK1.6.0r1 (without debug options turned on for vmxnet3 pmd) the igb_uio co= uld take over the vmxnet3 NIC but I encountered a core dump in the dev init= function for the vmxnet3 driver -- anybody encountered a similar issue ? I encountered these problems as well. - igb_uio module does not check if you disable vmxnet3-uio pmds, it will al= ways try to take over vmxnet3 devices. I have a patch waiting in my working dir to cleanly disable vmxnet3-uio pmd= . - If you don't bind vmxnet3 devices to uio, but forget to enable vmxnet3-us= ermap pmd (by specifiying -d librte_pmd_vmxnet3.so), then internal vmxnet3-= uio pmd will try to initialise and crash. I did not look any deeper into this, the easiest way is to disable vmxnet3-= uio pmd + apply the patch I will send in a few minutes, as a first workarou= nd. Regards, -- David Marchand =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