DPDK patches and discussions
 help / color / mirror / Atom feed
From: Srinivasreddy R <srinivasreddy4390@gmail.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] dpdk-16.07 : Does dpdk supports BCM5720
Date: Tue, 21 Mar 2017 16:31:25 +0530	[thread overview]
Message-ID: <CAJP4VWi4VKF4=YWij1YCxBBEJJdskKvNmwayPesKuJtNSt_rVg@mail.gmail.com> (raw)

Hi all,
I have "NetXtreme BCM5720 Gigabit Ethernet PCI" controllers .
I have binded to igb_uio . I have run l2fwd example .l2fwd saysno ports bye
.
Does BCM5720 works with dpdk .

./dpdk-stable-16.07.2/tools/dpdk-devbind.py --status

Network devices using DPDK-compatible driver
============================================0000:02:00.0 'NetXtreme
BCM5720 Gigabit Ethernet PCIe' drv=igb_uio unused=
0000:02:00.1 'NetXtreme BCM5720 Gigabit Ethernet PCIe' drv=igb_uio unused=
Network devices using kernel driver
===================================
0000:01:00.0 'NetXtreme BCM5720 Gigabit Ethernet PCIe' if=em1 drv=tg3
unused=igb_uio *Active*
0000:01:00.1 'NetXtreme BCM5720 Gigabit Ethernet PCIe' if=em2 drv=tg3
unused=igb_uio

Other network devices
=====================
<none>

*********************************************************************************************************


examples/l2fwd# ./build/app/l2fwd -c 0xf -m 1024 -n 3 -- -p 0x3
EAL: Detected 16 lcore(s)
EAL: No free hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
PMD: bnxt_rte_pmd_init() called for (null)EAL: Error - exiting with code: 1
  Cause: No Ethernet ports - bye


Document says :


*Broadcom NetXtreme-C®/NetXtreme-E® BCM5730X and BCM5740X family of
Ethernet Network Controllers*

thanks
srinivas

             reply	other threads:[~2017-03-21 11:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-21 11:01 Srinivasreddy R [this message]
2017-03-21 11:10 ` Ferruh Yigit
2017-03-21 11:36   ` Srinivasreddy R
2017-03-21 14:18     ` Ajit Khaparde

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='CAJP4VWi4VKF4=YWij1YCxBBEJJdskKvNmwayPesKuJtNSt_rVg@mail.gmail.com' \
    --to=srinivasreddy4390@gmail.com \
    --cc=dev@dpdk.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).