From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from jaguar.aricent.com (jaguar.aricent.com [121.241.96.11]) by dpdk.org (Postfix) with ESMTP id 4E7EC2E8A for ; Mon, 10 Mar 2014 12:23:04 +0100 (CET) Received: from jaguar.aricent.com (localhost [127.0.0.1]) by postfix.imss71 (Postfix) with ESMTP id 0AB9436B98; Mon, 10 Mar 2014 16:54:13 +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 E87A736B80; Mon, 10 Mar 2014 16:54:12 +0530 (IST) Received: from GUREXMB01.asian.ad.aricent.com ([10.203.171.132]) by GUREXHT02.ASIAN.AD.ARICENT.COM ([10.203.171.138]) with mapi; Mon, 10 Mar 2014 16:54:13 +0530 From: Chetan Bali To: Stefan Baranoff Date: Mon, 10 Mar 2014 16:54:10 +0530 Thread-Topic: [dpdk-dev] Intel 82571EB PMD support Thread-Index: Ac87oTJVsFdaf94zRT6tvORnkKUGggAAU7QUACwogAA= Message-ID: <8E6973B6CEA617469C62E4FDA1670F0640A9EC0803@GUREXMB01.ASIAN.AD.ARICENT.COM> References: <8E6973B6CEA617469C62E4FDA1670F0631B1532B38@GUREXMB01.ASIAN.AD.ARICENT.COM>, <8E6973B6CEA617469C62E4FDA1670F0631B10809B1@GUREXMB01.ASIAN.AD.ARICENT.COM> In-Reply-To: <8E6973B6CEA617469C62E4FDA1670F0631B10809B1@GUREXMB01.ASIAN.AD.ARICENT.COM> 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@dpdk.org" Subject: Re: [dpdk-dev] Intel 82571EB PMD support 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: Mon, 10 Mar 2014 11:23:04 -0000 Can anyone help me resolve this issue? We have bought the 82571EB dual port= NIC and we are not able to run the DPDK pmd userapp on it. Please update if there is any issue. -----Original Message----- From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Chetan Bali Sent: 09 March 2014 19:49 To: Stefan Baranoff Cc: dev@dpdk.org Subject: Re: [dpdk-dev] Intel 82571EB PMD support Hi Stefan, It will be of great help if you or anyone else could help me resolve this i= ssue. I have checked 82571EB on following setup: OS version: CentOS 6.4 [ kernel 2.6.32.358 ] DPDK version : DPDK 1.6.0-r1 Let me know if any update of centos can help resolve this issue? Thanks & Regards Chetan Bali ________________________________________ From: Stefan Baranoff [sbaranoff@gmail.com] Sent: Sunday, March 09, 2014 7:39 PM To: Chetan Bali Cc: dev@dpdk.org Subject: Re: [dpdk-dev] Intel 82571EB PMD support Chetan, I saw exactly that behavior with an 82599EB but running DPDK version 1.3.2 = and CentOS 6.2 and the fix for me was upgrading to CentOS 6.4 - there was a= thread a while back about a bug that caused DD to not be set but I can't s= eem to find it right now. I'm sorry I can't be of more help but at least this is a symptom that has b= een seen before. Regards, Stefan Sent from my smart phone; people don't make typos, Swype does! On Mar 7, 2014 5:18 AM, "Chetan Bali" > wrote: Hi, Do we have PMD support for intel 82571EB. We are having e1000e driver suppo= rted for 82571EB in linux. DPDK Version : 1.6.0-r1 Linux Kernel : CentOS 6.4 [ kernel version 2.6.32-358.el6.x86_64 ] Issue: When we run DPDK example [ l2fwd ], we are able to see successful init of r= te_pmd_em and link is also detected successfully. But the RX, TX count are zero. If we try to fetch nic stats using rte_eth_s= tats_get(), we can see around 256 ipacket count but after that error count = [rx error ] starts increasing. We are not able to see any packet on user app [ l2fwd ]. Does anyone else f= ace the same issue? Regards Chetan Bali =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 =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 =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