DPDK patches and discussions
 help / color / mirror / Atom feed
From: shiva m <anjaneya2@gmail.com>
To: "Wiles, Keith" <keith.wiles@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] rte_pmd_init_all is missing while upgrading from DPDK 1.6 to DPDK 1.7
Date: Mon, 30 May 2016 23:02:20 +0530	[thread overview]
Message-ID: <CAGm0vUpOnUk7zNFO8fPiRaGWHb1fpVWiYb7LGA2bjKbUMvXdeQ@mail.gmail.com> (raw)
In-Reply-To: <63E2EB50-3D10-4652-99D0-1026D67E7B14@intel.com>

Hi,

Thank you very much for your replies. I removed this API, I also see
rte_eal_pci_set_blacklist() is no more available with DPDK 1.7.1,  I am
using rte_eal_devargs_add(). Any document mentioning changes from DPDK-1.6
to DPDK-1.7?

Thanks,
Shiva

On Tue, May 24, 2016 at 11:32 AM, Wiles, Keith <keith.wiles@intel.com>
wrote:

> The PMD’s are now being inited in the EAL init call for the code and that
> API is not required anymore. If you are adding a new driver, make sure it
> is up to date with any changes in the driver code too.
>
> Regards,
> Keith
>
>
>
> >Hi,
> >
> >I have rte_pmd_init_all used in my code. While upgrading from DPDK 1.6 to
> >DPDK 1.7, I see this function is missing in DPDK 1.7. I
> >removed rte_pmd_init_all from my code, but I am not sure whether
> >initialization is done for all poll mode drivers
> >
> >What is the right way to do this?. Can anyone please help in this.
> >
> >Thanks,
> >Shiva
> >
>
>
>
>

      reply	other threads:[~2016-05-30 17:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-24  5:33 shiva m
2016-05-24  5:35 ` Zhang, Helin
2016-05-24  6:02 ` Wiles, Keith
2016-05-30 17:32   ` shiva m [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=CAGm0vUpOnUk7zNFO8fPiRaGWHb1fpVWiYb7LGA2bjKbUMvXdeQ@mail.gmail.com \
    --to=anjaneya2@gmail.com \
    --cc=dev@dpdk.org \
    --cc=keith.wiles@intel.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).