From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [PATCH v2] devargs: announce ABI change for device parameters Date: Wed, 10 May 2017 10:54:07 -0700 Message-ID: <20170510105407.0377a27c@xeon-e3> References: <4b1edeb12ff61bdb04a0189be30395589c713dbb.1494420483.git.gaetan.rivet@6wind.com> <1bb0b4a6403e42157ef983f0ee63320ce87a3996.1494430911.git.gaetan.rivet@6wind.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org To: Gaetan Rivet Return-path: Received: from mail-pg0-f44.google.com (mail-pg0-f44.google.com [74.125.83.44]) by dpdk.org (Postfix) with ESMTP id AF3851C00 for ; Wed, 10 May 2017 19:54:16 +0200 (CEST) Received: by mail-pg0-f44.google.com with SMTP id o3so1428076pgn.2 for ; Wed, 10 May 2017 10:54:16 -0700 (PDT) In-Reply-To: <1bb0b4a6403e42157ef983f0ee63320ce87a3996.1494430911.git.gaetan.rivet@6wind.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Wed, 10 May 2017 17:46:10 +0200 Gaetan Rivet wrote: > The PCI and virtual bus are planned to be moved to the generic > drivers/bus directory in v17.08. For this change to be possible, the EAL > must be made completely independent. > > The rte_devargs structure currently holds device representation internal > to those two busses. It must be made generic before this work can be > completed. > > Instead of using either a driver name for a vdev or a PCI address for a > PCI device, a devargs structure will have to be able to describe any > possible device on all busses, without introducing dependencies on > any bus-specific device representation. This will break the ABI for this > structure. > > Additionally, an evolution will occur regarding the device parsing > from the command-line. A user must be able to set which bus will handle > which device, and this setting is integral to the definition of a > device. > > The format has not yet been formally defined, but a proposition will > follow soon for a new command line parameter format for all devices. > > Signed-off-by: Gaetan Rivet I understand why having a union of all bus types is an issues since it means that if a new bus type (like VMBUS with GUID) has a bigger value then the existing representation would break. Perhaps give an example of what the new model would look like?