From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yuanhan Liu Subject: Re: [PATCH] drivers: make driver names consistent Date: Wed, 19 Oct 2016 18:05:43 +0800 Message-ID: <20161019100543.GQ16751@yliu-dev.sh.intel.com> References: <1472077494-164532-1-git-send-email-pablo.de.lara.guarch@intel.com> <10195497.iZAVVgVpbs@xps13> <20161018141837.GN16751@yliu-dev.sh.intel.com> <7993435.bReMuqSN60@xps13> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Jan Blunck , "De Lara Guarch, Pablo" , dev@dpdk.org, "Mcnamara, John" To: Thomas Monjalon Return-path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id B6A9F6936 for ; Wed, 19 Oct 2016 12:04:51 +0200 (CEST) Content-Disposition: inline In-Reply-To: <7993435.bReMuqSN60@xps13> 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" On Tue, Oct 18, 2016 at 06:46:40PM +0200, Thomas Monjalon wrote: > 2016-10-18 22:18, Yuanhan Liu: > > On Tue, Oct 18, 2016 at 03:42:54PM +0200, Thomas Monjalon wrote: > > > 2016-10-18 21:06, Yuanhan Liu: > > > > On Tue, Oct 18, 2016 at 02:50:16PM +0200, Jan Blunck wrote: > > > > > >From my understanding this is a massive API breakage. This forces all > > > > > existing users of the virtual PMDs to change with zero benefit. Even > > > > > if that isn't enough it also makes it impossible to switch between > > > > > releases by recompiling. > > > > > > > > > > Can we please revert these changes and work on some aliasing support > > > > > for the PMDs to fix it long term? > > > > > > > > +1. Aliasing is also something I would suggest before making such renames. > > > > > > It is a brutal change, yes. > > > It was announced in 16.07 release notes though. > > > > Yes, but it still took me a while (by running git bisect) to figure out > > what went wrong: I wasn't aware of such note, that I was thinking maybe > > something is broken. > > > > Later I also got quite few same complains. It may also took them a while > > to know what's happened. > > > > Anyway, my point is, for this kind of change, we should have added the > > alias support firstly. > > Yes. > > > If that's been done, then the announcement is not > > needed at all? > > The announcement would be needed to remove the aliases, later. Why do you have to remove an aliase? What's wrong if they stay there forever. I think the naming will be switched (maybe slowly) when we haved updated the doc (whereas it states "net_vhost" but not "eth_vhost" only). After few releases, the name should have been switched fluently. And we should not care about those alias. --yliu