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 26BD42A7 for ; Sun, 9 Mar 2014 07:01:59 +0100 (CET) Received: from jaguar.aricent.com (localhost [127.0.0.1]) by postfix.imss71 (Postfix) with ESMTP id 6D93936B30; Sun, 9 Mar 2014 11:33:07 +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 57C2436B28; Sun, 9 Mar 2014 11:33:07 +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; Sun, 9 Mar 2014 11:33:07 +0530 From: Chetan Bali To: "Jayakumar, Muthurajan" , "dev@dpdk.org" Date: Sun, 9 Mar 2014 11:28:48 +0530 Thread-Topic: Intel 82571EB PMD support Thread-Index: Ac857GCb99QEPXueQxGNqHGzW5rNYwA4aPYgAAZv8hAAHTfeUw== Message-ID: <8E6973B6CEA617469C62E4FDA1670F0631B10809B0@GUREXMB01.ASIAN.AD.ARICENT.COM> References: <8E6973B6CEA617469C62E4FDA1670F0631B1532B38@GUREXMB01.ASIAN.AD.ARICENT.COM> <8E6973B6CEA617469C62E4FDA1670F0631B10809AF@GUREXMB01.ASIAN.AD.ARICENT.COM>, <5D695A7F6F10504DBD9B9187395A21797C6EDB13@ORSMSX103.amr.corp.intel.com> In-Reply-To: <5D695A7F6F10504DBD9B9187395A21797C6EDB13@ORSMSX103.amr.corp.intel.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 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: Sun, 09 Mar 2014 06:01:59 -0000 Hi, Have checked this file too. It's listed and also init of pmd is fine and wo= rking since link is up. After sending the packets from directly connected interface, we are seeing = that rx nic stats are increasing but We are not seeing descriptor done status ( E1000_RX_STAT_DD ) set hence it = is not able to get the packet from rx software ring. Since the link is up, it should be able to receive the packets. Can anyone = help resolve this issue? Thanks & Regards Chetan Bali ________________________________________ From: Jayakumar, Muthurajan [muthurajan.jayakumar@intel.com] Sent: Saturday, March 08, 2014 9:52 PM To: Chetan Bali; dev@dpdk.org Subject: RE: Intel 82571EB PMD support Hi Chetan, 82571EB is supported - listed in http://dpdk.org/browse/dpdk/tree/lib/libr= te_eal/common/include/rte_pci_dev_ids.h Not heard issue before. RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, E1000_DEV_ID_82571EB_COPPER) RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, E1000_DEV_ID_82571EB_FIBER) RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, E1000_DEV_ID_82571EB_SERDES) RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, E1000_DEV_ID_82571EB_SERDES_DUA= L) RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, E1000_DEV_ID_82571EB_SERDES_QUA= D) RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, E1000_DEV_ID_82571EB_QUAD_COPPE= R) #define E1000_DEV_ID_82571EB_COPPER 0x105E #define E1000_DEV_ID_82571EB_FIBER 0x105F #define E1000_DEV_ID_82571EB_SERDES 0x1060 #define E1000_DEV_ID_82571EB_SERDES_DUAL 0x10D9 #define E1000_DEV_ID_82571EB_SERDES_QUAD 0x10DA #define E1000_DEV_ID_82571EB_QUAD_COPPER 0x10A4 Thanks, -----Original Message----- From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Chetan Bali Sent: Saturday, March 08, 2014 4:58 AM To: dev@dpdk.org Subject: Re: [dpdk-dev] Intel 82571EB PMD support Hi, anyone faced the same issue before? Thanks & Regards Chetan Bali ________________________________________ From: dev [dev-bounces@dpdk.org] On Behalf Of Chetan Bali Sent: Friday, March 07, 2014 3:48 PM To: dev@dpdk.org Subject: [dpdk-dev] Intel 82571EB PMD support 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