From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 8ADB12BE1 for ; Tue, 27 Jun 2017 18:02:28 +0200 (CEST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Jun 2017 09:01:44 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.39,401,1493708400"; d="scan'208";a="104196697" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.221.28]) by orsmga002.jf.intel.com with SMTP; 27 Jun 2017 09:01:40 -0700 Received: by (sSMTP sendmail emulation); Tue, 27 Jun 2017 17:01:39 +0100 Date: Tue, 27 Jun 2017 17:01:38 +0100 From: Bruce Richardson To: Gaetan Rivet Cc: dev@dpdk.org, Jan Blunck , Stephen Hemminger , Maxime Coquelin , Jerin Jacob , David Marchand Message-ID: <20170627160138.GD9796@bricha3-MOBL3.ger.corp.intel.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Research and =?iso-8859-1?Q?De=ACvel?= =?iso-8859-1?Q?opment?= Ireland Ltd. User-Agent: Mutt/1.8.1 (2017-04-11) Subject: Re: [dpdk-dev] [PATCH v5 0/7] rte_bus parse API X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jun 2017 16:02:29 -0000 On Wed, Jun 21, 2017 at 01:30:29AM +0200, Gaetan Rivet wrote: > Following the evolutions announced in [1], here is the first part of > the rte_devargs rework planned for 17.08. The rationale has been partially > explained in [2]. > > This first part covers the introduction of the necessary facilities in > rte_bus to allow for generic device parsing. This API is implemented for > the virtual and PCI buses. Additionally, this rte_bus evolution is being > used within rte_devargs to characterize a device type by its bus. > This work is the first of two parts to reduce the dependency of the EAL > upon specific bus implementations. > > Two public functions are added to rte_bus to help bus recognition: > > - rte_bus_from_name > - rte_bus_from_dev > > These functions are made public because the bus handle within devargs > becomes the generic device type. Recognizing device types is useful for > buses and PMDs alike. > The modified rte_devargs parsing allows declaring on the EAL command line > explicit buses to handle a device. The format is as follow: > > --vdev="virtual:net_ring0" --vdev="net_tap0,iface=tap0" > -w PCI:00:02.0 -w 00:03.0 > > This explicit bus designation is optional; no evolution is currently > forced on users to migrate to this new format. The separating character is > arbitrary and can be any character illegal within a bus name. > Subsequently, what is allowed within a bus name has been formally > defined and is now enforced. > > [1]: http://dpdk.org/ml/archives/dev/2017-May/065634.html > [2]: http://dpdk.org/ml/archives/dev/2017-May/065670.html > > This patchset depends on: > > bus: attach / detach API > http://dpdk.org/ml/archives/dev/2017-May/066330.html > http://dpdk.org/dev/patchwork/patch/24489/ > Just to note there are some errors on apply with this set after applying the latest version of the dependent patches. Nothing that's hard to fix, mind - this set just needs a new version after the attach/detach API set is applied. /Bruce