DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Shaw, Jeffrey B" <jeffrey.b.shaw@intel.com>
To: "hyunseok@ieee.org" <hyunseok@ieee.org>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] 82599ES NIC support
Date: Mon, 31 Mar 2014 17:38:46 +0000	[thread overview]
Message-ID: <4032A54B6BB5F04B8C08B6CFF08C59285540EDBB@FMSMSX103.amr.corp.intel.com> (raw)
In-Reply-To: <CAAJNysLJmCFU+r9cy9KGRfYWWt+Gn-ci6vb2Nh15_r_TKcpHXw@mail.gmail.com>

Can you check if your PCI device ID is listed in "lib/librte_eal/common/include/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_*" options, 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 DPDK 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 former to fail to work with DPDK?

Is it possible to fix this problem?  I'll be glad to help fix it.

Thanks,
-HS

  reply	other threads:[~2014-03-31 17:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-31 17:29 HS
2014-03-31 17:38 ` Shaw, Jeffrey B [this message]
2014-03-31 18:16   ` HS
2014-03-31 18:46     ` Shaw, Jeffrey B
2014-04-01 20:29       ` HS

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4032A54B6BB5F04B8C08B6CFF08C59285540EDBB@FMSMSX103.amr.corp.intel.com \
    --to=jeffrey.b.shaw@intel.com \
    --cc=dev@dpdk.org \
    --cc=hyunseok@ieee.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).