DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: raman geetha gopalakrishnan <glowingsun@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Reg DPDK & PMD
Date: Wed, 8 Mar 2017 14:16:58 +0000	[thread overview]
Message-ID: <20170308141658.GA292076@bricha3-MOBL3.ger.corp.intel.com> (raw)
In-Reply-To: <CABAuC=ks2efJLTGAnpuMs47qtvrAtm9eo5DfdHRuDPiTPSr0ag@mail.gmail.com>

On Wed, Mar 08, 2017 at 07:05:03PM +0530, raman geetha gopalakrishnan 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?

No, that assumption is not correct, which is the reason we have so many
NIC drivers in DPDK. Each NIC uses a different method of talking to SW,
both in terms of the registers needed to be accessed to initialize the
NIC and then in terms of the metadata format used to receive or transmit
packets.

Regards,
/Bruce

> 
>      B) if #A is correct , how can i make changes to PMD to support any NIC
> ?
> 
> if i have to put the above question in different way then it is
> 
> 2. what is preventing us from having a common PMD layer for all NICs and
> additional PMD specific to each NIC???
> 
> Thanks
> Raman

  reply	other threads:[~2017-03-08 14:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-08 13:35 raman geetha gopalakrishnan
2017-03-08 14:16 ` Bruce Richardson [this message]
2017-03-09  3:16   ` raman geetha gopalakrishnan
2017-03-08 14:25 ` Ferruh Yigit
2017-03-08 14:37   ` Wiles, Keith

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=20170308141658.GA292076@bricha3-MOBL3.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=glowingsun@gmail.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).