From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Roger B. Melton" Subject: Re: Making rte_eal_pci_probe() in rte_eal_init() optional? Date: Sat, 14 Nov 2015 10:55:18 -0500 Message-ID: <56475966.2080404@cisco.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: "dev@dpdk.org" To: Don Provan , David Marchand Return-path: Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) by dpdk.org (Postfix) with ESMTP id E4A0595B6 for ; Sat, 14 Nov 2015 16:55:17 +0100 (CET) In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Agreed. For our application, the debug case would be to _enable_ the PCI scan. Again, thanks David for pointing it out. It did solve our problem. Regards, Roger On 11/13/15 5:58 PM, Don Provan 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. > > -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 > 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. > ... >