From: "Jia.Sui(贾睢)" <Jia.Sui@advantech.com.cn>
To: ankit kumar <akprajapati616@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK support for Intel 82546EB Gigabit Ethernet Controller
Date: Mon, 22 Jul 2013 17:16:10 +0800 [thread overview]
Message-ID: <581E2E1085FAEF45B48CF8A139824CF804E6356745@ACNMAIL1.ACN.ADVANTECH.CORP> (raw)
In-Reply-To: <CAG9qd2o3JbiDupXfYbZijN3V5wqanzc2DOdna_WHvGcOMRVjMQ@mail.gmail.com>
Hi Ankit Kumar,
It looks your NIC is not supported by Intel DPDK.
You can have a view on "RTE_SDK/lib/librte_eal/common/include/rte_pci_dev_ids.h
This file shows which device was supported in Intel DPDK. :)
we can see that Intel 82562 and Intel 82546 were not supported in DPDK r1.2.3
Maybe it will supported in future version.
Thanks
Best Regards
Jia Sui
-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of ankit kumar
Sent: Monday, July 22, 2013 5:04 PM
To: dev@dpdk.org
Subject: [dpdk-dev] DPDK support for Intel 82546EB Gigabit Ethernet Controller
HI,
Recently i was trying to work with intel DPDK but when i tried
with test example as "l2fwd" it shows as “No Ethernet ports – bye”.
i have 4 NICs.
#lspci |grep "Ethernet"
00:19.0 Ethernet controller: Intel Corporation 82562V-2 10/100 Network
Connection (rev 02)
02:00.0 Ethernet controller: Intel Corporation 82546EB Gigabit
Ethernet Controller (Copper) (rev 03)
02:00.1 Ethernet controller: Intel Corporation 82546EB Gigabit
Ethernet Controller (Copper) (rev 03)
02:01.0 Ethernet controller: D-Link System Inc DGE-528T Gigabit
Ethernet Adapter (rev 10)
What may be the reason? is it due to NIC as "Intel 82546EB Gigabit
Ethernet Controller" or anything else.
Please suggest.
Thanks and Best Regards
Ankit Kumar
prev parent reply other threads:[~2013-07-22 9:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 9:04 ankit kumar
2013-07-22 9:15 ` Thomas Monjalon
2013-07-22 9:16 ` Jia.Sui [this message]
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=581E2E1085FAEF45B48CF8A139824CF804E6356745@ACNMAIL1.ACN.ADVANTECH.CORP \
--to=jia.sui@advantech.com.cn \
--cc=akprajapati616@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).