From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id D661B2E8E for ; Mon, 31 Mar 2014 19:37:19 +0200 (CEST) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga101.jf.intel.com with ESMTP; 31 Mar 2014 10:38:53 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.97,766,1389772800"; d="scan'208";a="484176287" Received: from fmsmsx105.amr.corp.intel.com ([10.19.9.36]) by orsmga001.jf.intel.com with ESMTP; 31 Mar 2014 10:38:48 -0700 Received: from fmsmsx158.amr.corp.intel.com (10.18.116.75) by FMSMSX105.amr.corp.intel.com (10.19.9.36) with Microsoft SMTP Server (TLS) id 14.3.123.3; Mon, 31 Mar 2014 10:38:47 -0700 Received: from fmsmsx103.amr.corp.intel.com ([169.254.3.218]) by fmsmsx158.amr.corp.intel.com ([169.254.15.20]) with mapi id 14.03.0123.003; Mon, 31 Mar 2014 10:38:47 -0700 From: "Shaw, Jeffrey B" To: "hyunseok@ieee.org" , "dev@dpdk.org" Thread-Topic: [dpdk-dev] 82599ES NIC support Thread-Index: AQHPTQb8DcDCcln1dESibtumRCjM8Zr7dLTA Date: Mon, 31 Mar 2014 17:38:46 +0000 Message-ID: <4032A54B6BB5F04B8C08B6CFF08C59285540EDBB@FMSMSX103.amr.corp.intel.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.1.200.106] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] 82599ES NIC 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, 31 Mar 2014 17:37:20 -0000 Can you check if your PCI device ID is listed in "lib/librte_eal/common/inc= lude/rte_pci_dev_ids.h"? Can you verify that you have bound your device to "igb_uio", perhaps using = "tools/pci_unbind.py" (maybe renamed to tools/igb_uio_bind.py)? You might also try to edit the ".config" (in your build directory, NOT the = Linux .config) to enable any of the "CONFIG_RTE_LIBRTE_IXGBE_DEBUG_*" optio= ns, in case there are more error messages. Thanks, Jeff -----Original Message----- From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of HS Sent: Monday, March 31, 2014 10:30 AM To: dev@dpdk.org Subject: [dpdk-dev] 82599ES NIC support Hi, I was trying to test DPDK 1.6 with "82599ES" Intel NIC, but noticed that DP= DK does not seem to work with this NIC. DPDK app fails because rte_eth_dev_count() returns 0. On the other hand, I confirmed DPDK works okay with "82599EB". So looks like not all 82599 (ixgbe) chipsets are supported by DPDK while it= says so in http://dpdk.org/doc/nics What is the discrepancy between 82599ES and 82599EB, which causes the forme= r to fail to work with DPDK? Is it possible to fix this problem? I'll be glad to help fix it. Thanks, -HS