DPDK usage discussions
 help / color / mirror / Atom feed
From: raman geetha gopalakrishnan <glowingsun@gmail.com>
To: "Wiles, Keith" <keith.wiles@intel.com>
Cc: users <users@dpdk.org>
Subject: Re: [dpdk-users] Reg DPDK & PMD
Date: Thu, 9 Mar 2017 08:45:12 +0530	[thread overview]
Message-ID: <CABAuC==5oHwNK9TAYqDa=5U1PuPAMuN20Y+kzP3sp4=Scgb=3A@mail.gmail.com> (raw)
In-Reply-To: <629169D5-EAC6-425D-A126-9ECB85F7EE21@intel.com>

Hi Keith,

Thanks for providing a detail answer. As i understood for the application
to have the same interface ethdev exposes a common API which gets
implemented by each PMD specifically based on the NIC it supports. My basic
assumption of all NIC having some common operating procedure is not
correct. Thanks for your time.

Thanks
Raman

On Wed, Mar 8, 2017 at 8:25 PM, Wiles, Keith <keith.wiles@intel.com> wrote:

>
> > On Mar 8, 2017, at 7:29 AM, raman geetha gopalakrishnan <
> glowingsun@gmail.com> wrote:
> >
> > Hi All,
> >
> > I have just rephrased by last question to understand
> > 1. *what is preventing us from having a common PMD layer for all NICs and
> > additional PMD specific to each NIC???*
>
> We do have a common layer it is called the ethdev layer. The ethdev layer
> provides a common and generic API’s for the application to use and requires
> PMDs to register a set of function pointers to ethdev. These function
> pointers are common and generic to all of the PMDs. As for the PMDs it is
> impossible to have a cleaner solution unless every NIC is programmed in the
> same why. The two layer device model is used in just about all OS types
> like Linux, Windows, FreeBSD, … as this appears to be the best solution
> until you can get every vendor in the world to pick a single hardware
> interface.
>
> >
> > Thanks
> > Raman
>
> Regards,
> Keith
>
>

      reply	other threads:[~2017-03-09  3:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-08 13:29 raman geetha gopalakrishnan
2017-03-08 14:55 ` Wiles, Keith
2017-03-09  3:15   ` raman geetha gopalakrishnan [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='CABAuC==5oHwNK9TAYqDa=5U1PuPAMuN20Y+kzP3sp4=Scgb=3A@mail.gmail.com' \
    --to=glowingsun@gmail.com \
    --cc=keith.wiles@intel.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).