From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-f66.google.com (mail-lf0-f66.google.com [209.85.215.66]) by dpdk.org (Postfix) with ESMTP id 76D2311C5 for ; Thu, 7 Apr 2016 10:23:10 +0200 (CEST) Received: by mail-lf0-f66.google.com with SMTP id t203so3580214lfd.0 for ; Thu, 07 Apr 2016 01:23:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=OFLpFf2a4DE3HGuBaF3hbhc4hSKB76Iz/2zpwB4n4aM=; b=bg8o5n3TxAByY0h0uDr+ieBsYCBhrv9K37mptNeyHKNJyOQc9zax4Je7gFi7iyIaLC 0GrqQVjvQsP6hWnaZfQ0gZz0GiMd014yMjuCLfSefMSYOHZ8NXqt5+sVUF+Eiz7iAyD1 qQiczS3GJ04WhzcVYUvBZ9AkGgXc6ycDfzkhmSwYu3oo4a/Zf7pmzEB16wNMR0bICuhw zYXvraofFMO04cJbre1B7DNpY3+a/43nlcVqvPxACS3AD2a3vJhHkHmTTinMcL2tWsDm 6Eiv5UKIRP21ko/gb8hnHnS1wp3MP35kx93bmsfF5rkhuYrPpSi6oP9725HACuWKERha 5nhg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=OFLpFf2a4DE3HGuBaF3hbhc4hSKB76Iz/2zpwB4n4aM=; b=GktVcnqwq3tbNtNkiLPqfI1RXrBGfXWiD/+zwaDfbJSWZ6uWquqNTT63bxDzobCka2 IgWVm1GnSOiaPVDU4o97nDjP3/cuusM6Be66aDNZOPf+TMyHrIEhGDof2gdCK5+l2ioM maZ08rVTJMz076xvg01rozmEbiWn1jTbb9gRJ/Odp9EuTv52uVItI3hYM9x5YXnDmJPF 2PhV3cjxNny6aYYgx1TB95YhzkD5I8Z60bRe+qhf447RHp3KVLxSMyX0Ga1zGSbVk1RB Gxs4DG4h5GJ83g7RgcNymlcV1EnGxxTDlPuFO+y81mksxZJ9lUaqFXt7bNRCQO94jjdW RZCA== X-Gm-Message-State: AD7BkJKn4oz1NsYLSsHXsh3hd+m0KqP3X9Qpv3GtkaIbZUb2hQi+oTE/G0kiaFfKR1t0NdtTC3csvJyx5Nri4A== X-Received: by 10.25.137.215 with SMTP id l206mr679817lfd.140.1460017390007; Thu, 07 Apr 2016 01:23:10 -0700 (PDT) MIME-Version: 1.0 Sender: marc.sune@gmail.com Received: by 10.25.156.72 with HTTP; Thu, 7 Apr 2016 01:22:50 -0700 (PDT) In-Reply-To: <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> <57056FD8.70602@redhat.com> From: Marc Date: Thu, 7 Apr 2016 10:22:50 +0200 X-Google-Sender-Auth: 7h-hPy47LYfBXTr8KJVcyl7UFXo Message-ID: To: Dave Neary Cc: Panu Matilainen , Yuanhan Liu , Arnon Warshavsky , "Trahe, Fiona" , Thomas Monjalon , "dev@dpdk.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] DPDK namespace X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Apr 2016 08:23:10 -0000 On 6 April 2016 at 22:21, Dave Neary wrote: > 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. > +1 Either all types and symbols use dpdk_ or rte_. It probably makes more sense dpdk_, but to me it is not that important. If it has to be changed, it might be a good idea to do it in this release, now that version numbering format also changes. > > > 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. > You would also have to add all typedefs for type names. Why bothering? Moving from 2.2 to 16.04 requires recompiling your application (ABI changes), and is as simple as sed -e 's/rte_/dpdk_/g' in all the application code base. Marc > > 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 >