From: Farrukh Aftab Khan <Farrukh.Khan@xflowresearch.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] The type of ethernet card that DPDK require
Date: Fri, 28 Jun 2013 16:58:42 +0500 [thread overview]
Message-ID: <CAOKjMzsQdxOiqVyb+9w7H2wbR6k=emd0W0NnP0-TqFjbQdnXwQ@mail.gmail.com> (raw)
In-Reply-To: <201306281028.02095.thomas.monjalon@6wind.com>
[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]
Hi Thomas,
Thanks for the clarification and explanation. Much appreciated.
I guess it becomes a little hard for people who have just started working
with DPDK to figure that out.
Thanks for the help.
Best regards.
-
Farrukh Aftab Khan
On Fri, Jun 28, 2013 at 1:28 PM, Thomas Monjalon
<thomas.monjalon@6wind.com>wrote:
> 28/06/2013 08:39, dvr :
> > I'm confused which type of ethernet card that DPDK require.
>
> OK. Since this type of question has already been asked and will probably be
> asked again and again, I will explain it on the website.
>
> For the record, here is how you should search for a supported NIC:
>
> # grep -r 'RTE_PCI_DEV_ID_DECL.*82575' lib
> RTE_PCI_DEV_ID_DECL(PCI_VENDOR_ID_INTEL, E1000_DEV_ID_82575EB_COPPER)
> RTE_PCI_DEV_ID_DECL(PCI_VENDOR_ID_INTEL,
> E1000_DEV_ID_82575EB_FIBER_SERDES)
> RTE_PCI_DEV_ID_DECL(PCI_VENDOR_ID_INTEL, E1000_DEV_ID_82575GB_QUAD_COPPER)
>
> So your NIC 82575EB is supported.
>
> As you can see, the source code is a good documentation.
> To all users, please try to search in it before asking questions.
> --
> Thomas
>
[-- Attachment #2: Type: text/html, Size: 2267 bytes --]
prev parent reply other threads:[~2013-06-28 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 6:39 dvr
2013-06-28 7:03 ` Farrukh Aftab Khan
[not found] ` <4a63f461.258b3.13f89c20286.Coremail.jinxiu.1006@163.com>
2013-06-28 8:11 ` Farrukh Aftab Khan
2013-06-28 8:28 ` Thomas Monjalon
2013-06-28 11:58 ` Farrukh Aftab Khan [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='CAOKjMzsQdxOiqVyb+9w7H2wbR6k=emd0W0NnP0-TqFjbQdnXwQ@mail.gmail.com' \
--to=farrukh.khan@xflowresearch.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).