From: Nikhil Nanal <nanal@usc.edu>
To: raman geetha gopalakrishnan <glowingsun@gmail.com>
Cc: users <users@dpdk.org>
Subject: Re: [dpdk-users] Reg PMD & NIC
Date: Tue, 7 Mar 2017 23:11:43 -0800 [thread overview]
Message-ID: <6E71A877-544C-4DAD-B7DD-CDE8F20CDA07@usc.edu> (raw)
In-Reply-To: <CABAuC=nZPH-OzsvZn2xPZUKxEFBOkAau78FhxX7BwfZEeLhp_Q@mail.gmail.com>
Hi,
I guess DPDK works only for Intel NICs. Also, there are a variety of NIC cards from Intel.
The drivers are generally specific to a NIC card or a family of NIC cards. The DPDK, replaces the existing NIC drivers with its PMD drivers, , but these PMDs are
only compatible with some specified class of Intel NIC cards and so there are only some supported NICs but not all.
thanks
Nikhil
> On Mar 7, 2017, at 11:05 PM, raman geetha gopalakrishnan <glowingsun@gmail.com> wrote:
>
> Hi All,
>
> I have the following basic question. Hope to get an answer / link where i
> can get myself clear.
>
> 1. In DPDK PMD is optimized driver for an given NIC to get maximum
> performance.
> That being the case why we are talking about DPDK supported NICs.
>
> A) My assumption is that NIC interface is standardized so that PMD
> should actually work with any NIC (barring some NIC specific performance
> tweaks)
> is that correct?
>
> B) if #A is correct , how can i make changes to PMD to support any NIC
> ?
>
>
> Thanks
> Raman
next prev parent reply other threads:[~2017-03-08 7:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 7:05 raman geetha gopalakrishnan
2017-03-08 7:11 ` Nikhil Nanal [this message]
2017-03-08 7:40 ` raman geetha gopalakrishnan
2017-03-08 10:03 ` Thomas Monjalon
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=6E71A877-544C-4DAD-B7DD-CDE8F20CDA07@usc.edu \
--to=nanal@usc.edu \
--cc=glowingsun@gmail.com \
--cc=users@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).