DPDK usage discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Nagaprabhanjan Bellaru <nagp.lists@gmail.com>
Cc: users@dpdk.org, "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
Subject: Re: [dpdk-users] Not able to detect Intel EC I218-V (rev 03)
Date: Fri, 26 Feb 2016 21:54:41 +0100	[thread overview]
Message-ID: <1832989.9gGstv1zq5@xps13> (raw)
In-Reply-To: <CABDVJk-erAbYo=yZC2hkSMHBEjEiq3+g-rh6a6YixUFn-6ekpA@mail.gmail.com>

Hi,

2016-02-26 18:59, Nagaprabhanjan Bellaru:
> Hello,
> 
> Using setup.sh (available in tools folder) I have bound eth0 (which is of
> Intel EC I218-V make) to igb_uio module (which I can see with
> dpdk_nic_bind.py --status output):
> 
> --
> Network devices using DPDK-compatible driver
> ============================================
> 0000:00:19.0 'Ethernet Connection (3) I218-V' drv=igb_uio unused=
> 
> Network devices using kernel driver
> ===================================
> <none>
> --
> 
> However, when I run any sample application, it complains that there are no
> ethernet ports:
> 
> --
> EAL: Error - exiting with code: 1
>   Cause: No available NIC ports!
> --
> 
> If I give a --vdev=eth_pcap0,iface=eth0, then it picks it. Am I missing
> something? I hope this Intel card is supported by DPDK.

I think this card is not supported.
We are waiting a review for this patch:
	http://dpdk.org/dev/patchwork/patch/7161/
Do not hesitate to test it.

  reply	other threads:[~2016-02-26 20:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26 13:29 Nagaprabhanjan Bellaru
2016-02-26 20:54 ` Thomas Monjalon [this message]
2016-02-27 10:38   ` Nagaprabhanjan Bellaru
2016-02-27 17:16     ` Thomas Monjalon
2016-02-28  0:59       ` Ravi Kerur
2016-02-29  0:54         ` Lu, Wenzhuo
2016-03-15 14:32           ` Nagaprabhanjan Bellaru

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=1832989.9gGstv1zq5@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=nagp.lists@gmail.com \
    --cc=users@dpdk.org \
    --cc=wenzhuo.lu@intel.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).