From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [RFC PATCH 0/6] Restructure EAL device model for bus support Date: Mon, 21 Nov 2016 10:08:32 +0100 Message-ID: <29033576.pHDTdAbKFW@xps13> References: <1479360605-20558-1-git-send-email-shreyansh.jain@nxp.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: David Marchand , Shreyansh Jain , Jan Blunck To: dev@dpdk.org Return-path: Received: from mail-wm0-f41.google.com (mail-wm0-f41.google.com [74.125.82.41]) by dpdk.org (Postfix) with ESMTP id 383DB2934 for ; Mon, 21 Nov 2016 10:08:36 +0100 (CET) Received: by mail-wm0-f41.google.com with SMTP id g23so134369016wme.1 for ; Mon, 21 Nov 2016 01:08:36 -0800 (PST) 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" 2016-11-20 16:30, David Marchand: > For a first patchset, I would see: > - introduce the rte_bus object. In rte_eal_init, for each bus, we call > the scan method. Then, for each bus, we find the appropriate > rte_driver using the bus match method then call the probe method. If > the probe succeeds, the rte_device points to the associated > rte_driver, > - migrate the pci scan code to a pci bus (scan looks at sysfs for > linux / ioctl for bsd + devargs for blacklist / whitelist ?), match is > the same at what is done in rte_eal_pci_probe_one_driver() at the > moment, > - migrate the vdev init code to a vdev bus (scan looks at devargs): > this is new, we must create rte_device objects for vdev drivers to use > later I think it can be 3 patchsets. Who can work on the vdev part please? > Then we can talk about the next steps once the bus is in place. Yes