DPDK patches and discussions
 help / color / mirror / Atom feed
From: Henry Wang <wang_hr@neusoft.com>
To: "Rui Vaz (ruvaz)" <ruvaz@cisco.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] rte_eth_dev_count() returns 0
Date: Fri, 10 May 2013 09:18:04 +0800	[thread overview]
Message-ID: <CAE68AUOr7B5a2QvduJhH0kEHPi+sR9X3qfrtumgLxT1BK4VS+Q@mail.gmail.com> (raw)
In-Reply-To: <AFCFCEB8EB0E24448E4EB95988BA1E531FA2EA0D@xmb-aln-x05.cisco.com>

[-- Attachment #1: Type: text/plain, Size: 2234 bytes --]

As far as I known, DPDK(1.2.3) only supports the following NICs:
(1) Intel 82576, 82580, I350 chipset based NICs;
(2) Intel 82599, X540T, X520T chipset based NICs;
(3) virtual NICs generated by SR-IOV from (2).

If the NICs on your C220 M3 is one of (2), you can run l2fwdvf OR l3fwdvf
successfully with SR-IOV enabled in ESXi.
And I do not know wheather ESXi 5.0 VMM has SR-IOV function or not.

Further more, please reference to DPDK release notes.
http://www.intel.com/content/dam/www/public/us/en/documents/release-notes/intel-dpdk-release-notes.pdf



On Fri, May 10, 2013 at 9:00 AM, Rui Vaz (ruvaz) <ruvaz@cisco.com> wrote:

>  Hi dev-dpdk,****
>
> ** **
>
> I am following a Intel DPDK Step by Step Instruction found here:
> http://www.slideshare.net/hisaki/intel-dpdk-step-by-step-instructions****
>
> My Hello app from the DPDK examples runs fine, but I get the following
> error when running the l2fwd app:****
>
> ** **
>
> “EAL: Error – exiting with code: 1****
>
> Cause: no Ethernet ports – bye”****
>
> ** **
>
> The rte_eth_dev_count() call returns 0, I am using a CentOS 6.3 Virtual
> Machine on VMWare esxi 5.0 on a Cisco UCS C220 M3 which comes with Xeon
> E5-2600.  ****
>
> ** **
>
> I would really appreciate If you could provide some help to solve this
> issue.****
>
> ** **
>
> Thank you,****
>
> Rui****
>
> ** **
>
---------------------------------------------------------------------------------------------------
Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) 
is intended only for the use of the intended recipient and may be confidential and/or privileged of 
Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is 
not the intended recipient, unauthorized use, forwarding, printing,  storing, disclosure or copying 
is strictly prohibited, and may be unlawful.If you have received this communication in error,please 
immediately notify the sender by return e-mail, and delete the original message and all copies from 
your system. Thank you. 
---------------------------------------------------------------------------------------------------

[-- Attachment #2: Type: text/html, Size: 3907 bytes --]

  reply	other threads:[~2013-05-10  1:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-10  1:00 Rui Vaz (ruvaz)
2013-05-10  1:18 ` Henry Wang [this message]
2013-05-10 16:05   ` Bhavesh Davda
2013-05-10 16:15     ` Stephen Hemminger
2013-05-10 16:21       ` Bhavesh Davda
2013-05-10 18:44         ` Stephen Hemminger
2013-05-10 19:10           ` Bhavesh Davda
2013-05-10 19:29             ` Stephen Hemminger
2013-05-10 21:00               ` Bhavesh Davda
2013-05-18  0:09   ` Rui Vaz (ruvaz)
2013-05-10 15:47 ` Vincent JARDIN

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=CAE68AUOr7B5a2QvduJhH0kEHPi+sR9X3qfrtumgLxT1BK4VS+Q@mail.gmail.com \
    --to=wang_hr@neusoft.com \
    --cc=dev@dpdk.org \
    --cc=ruvaz@cisco.com \
    /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).