DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jan Viktorin <viktorin@rehivetech.com>
To: Don Provan <dprovan@bivio.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Making rte_eal_pci_probe() in rte_eal_init() optional?
Date: Sat, 14 Nov 2015 00:03:08 +0100	[thread overview]
Message-ID: <20151114000308.28bc0633@jvn> (raw)
In-Reply-To: <CY1PR0101MB0987905CF30EEB09DAD6259DA0110@CY1PR0101MB0987.prod.exchangelabs.com>

On Fri, 13 Nov 2015 22:58:04 +0000
Don Provan <dprovan@bivio.net> wrote:

> --no-pci is cool. I'm pretty sure that wasn't there when the PCI scan was first added to
> the library init routine. I'm glad to see it, so thanks for pointing it out.
> 
> Just for the record: The comment says, "for debug purposes, PCI can be disabled".
> This exhibits one of those classic DPDK blindspots. The library can be used for many
> things entirely unrelated to hardware. My project has several DPDK applications
> intended to be used by users that do not have privs to mess around with PCI
> hardware, so, for them, turning off PCI wouldn't be just for debugging purposes.

And ARMv7 depends on this option a bit... just for the record ;).

Jan

> 
> -don provan
> dprovan@bivio.net
> 
> -----Original Message-----
> From: David Marchand [mailto:david.marchand@6wind.com] 
> Sent: Friday, November 13, 2015 12:50 AM
> To: Roger B Melton <rmelton@cisco.com>
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] Making rte_eal_pci_probe() in rte_eal_init() optional?
> 
> ...
> Did you try the --no-pci option ?
> It avoids the initial sysfs scan, so with no pci device, the initial pci_probe should do nothing.
> ...
> 

  reply	other threads:[~2015-11-13 23:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-13 22:58 Don Provan
2015-11-13 23:03 ` Jan Viktorin [this message]
2015-11-14 15:55 ` Roger B. Melton
2015-11-14 17:51   ` David Marchand
2015-11-15 14:45     ` Roger B. Melton
2015-11-16  9:46       ` David Marchand
2015-11-17 13:56         ` Roger B. Melton
2015-11-17 15:46           ` Thomas Monjalon
2015-11-18 22:13             ` Roger B. Melton
2015-11-21 12:54               ` Roger B. Melton
  -- strict thread matches above, loose matches on Subject: below --
2015-11-12 22:43 Roger B Melton
2015-11-13  8:49 ` David Marchand
2015-11-13 12:07   ` Roger B. Melton

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=20151114000308.28bc0633@jvn \
    --to=viktorin@rehivetech.com \
    --cc=dev@dpdk.org \
    --cc=dprovan@bivio.net \
    /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).