From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Neary Subject: Re: DPDK namespace Date: Wed, 6 Apr 2016 16:21:44 -0400 Message-ID: <57056FD8.70602@redhat.com> References: <1610488.T03Kyi0Reo@xps13> <348A99DA5F5B7549AA880327E580B43588FC621D@IRSMSX101.ger.corp.intel.com> <20160406052656.GT3080@yliu-dev.sh.intel.com> <5704FC10.8020405@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: "Trahe, Fiona" , Thomas Monjalon , "dev@dpdk.org" To: Panu Matilainen , Yuanhan Liu , Arnon Warshavsky Return-path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 0031A2C0B for ; Wed, 6 Apr 2016 22:21:47 +0200 (CEST) In-Reply-To: <5704FC10.8020405@redhat.com> 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" Hi, On 04/06/2016 08:07 AM, Panu Matilainen wrote: >> +1: it's a bit weird to keep both, especially for a long while, that >> every time we turn a rte_ prefix to dpdk_ prefix, we break applications. >> Instead of breaking applications many times, I'd prefer to break once. >> Therefore, applications could do a simple global rte_ -> dpdk_ >> substitute: >> it doesn't sound that painful then. > > I concur. If (and I think that should be a pretty big IF) the prefix is > to be changed then its better done in one fast sweep than gradually. > > Gratuitious (or nearly so) change is always extremely annoying, and the > longer it takes the more painful it is. Application developers wont much > care what the prefix is as long as its consistent, but if they're forced > to track prefix changes across several releases with different libraries > moving at different pace, they WILL be calling for bloody murder :) How about the idea of creating (at switch over time) an optionally installable dpdk_compat package that just has a list of #defines for the old symbols pointing them at the new symbols? That would also allow people with old applications to update DPDK without having to modify their applications. Thanks, Dave. -- Dave Neary - NFV/SDN Community Strategy Open Source and Standards, Red Hat - http://community.redhat.com Ph: +1-978-399-2182 / Cell: +1-978-799-3338