From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vk0-f46.google.com (mail-vk0-f46.google.com [209.85.213.46]) by dpdk.org (Postfix) with ESMTP id 27F0B2C06 for ; Wed, 6 Apr 2016 14:41:08 +0200 (CEST) Received: by mail-vk0-f46.google.com with SMTP id e6so56161089vkh.2 for ; Wed, 06 Apr 2016 05:41:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=infinite-io.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=A71RTABaUZ7UmIVCi6yhk4y4ZxqH2OpMvySzr6JLfsI=; b=eXET+PzTSql1uUw8KsKUymn2YlzQPupvtFem9PCjjTrGTruJEOagHCC5Jt3tMkRzKn SteopRe7P8rNMCgAZgMNeopeaa7/h40DikxSCc+9UlxMldcdqakoy/c+CHVptK4cFXH+ SZPNgZpAwcsrn4diea5bT2zXaQbivNtc14W+T9R16Q2Qr90BKweXi9g6AgjZF8SYouWD PxiGGugxhZzYC7Zs6Opz9I+Zk8nz0AtwE8iVndRSwjCxqxP8bBRSvuSv+GXpcZL3ilce kAQBBDgxVLmpCpvV3zFHWiHF7ZzfvZHFJu7xqJsDyOeb7U4pRIgsPv0d0ZsyOKS2qNdy feiA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=A71RTABaUZ7UmIVCi6yhk4y4ZxqH2OpMvySzr6JLfsI=; b=iMsHxS0kO5MHank4ldyDQM1meQvamynyzaK0WH+gInvOTpQ94jmI2mjxN5/Mf4LyN+ bQvTnSSQYRUJXSUNvD08KsO7kOvar413RSxI8QpZL+M6BX6GW5/3hLNHoQOgfvtShrwe b7irbW+nTeD1Pi47y33hRQ/MAxVN8w7n/0PtS/SRx4KH6iJ8nPdfvGbhrXHz5kNBjR1Q cfZdsMO2PrRuhZAzmCPhdztJemQFkG+AB8LoW3ZzkOUN1gChG/Spdli7F8yhHOiLbtq2 hu2X+VRSlKibGdneNEBcv6pTE940pm60/byyPrvdbIFkgmlK06MF+kPGh+c861RIUo8U 9AQA== X-Gm-Message-State: AD7BkJK8q1BocUku8htbjb+6/IZfdw5Yvw0BTt8GL9CGT18FO2Od1PdSfiv+luZabmqlaJu2zh7lGURprCU1YA== MIME-Version: 1.0 X-Received: by 10.176.0.8 with SMTP id 8mr6819963uai.67.1459946467582; Wed, 06 Apr 2016 05:41:07 -0700 (PDT) Received: by 10.103.86.14 with HTTP; Wed, 6 Apr 2016 05:41:07 -0700 (PDT) In-Reply-To: <20160406052656.GT3080@yliu-dev.sh.intel.com> References: <1610488.T03Kyi0Reo@xps13> <348A99DA5F5B7549AA880327E580B43588FC621D@IRSMSX101.ger.corp.intel.com> <20160406052656.GT3080@yliu-dev.sh.intel.com> Date: Wed, 6 Apr 2016 07:41:07 -0500 Message-ID: From: Jay Rolette To: Yuanhan Liu Cc: 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: Wed, 06 Apr 2016 12:41:08 -0000 On Wed, Apr 6, 2016 at 12:26 AM, Yuanhan Liu wrote: > On Tue, Apr 05, 2016 at 05:31:22PM +0300, Arnon Warshavsky wrote: > > Googling rte functions or error codes usually takes you to dpdk dev email > > archive so I don't think it is that much difficult to figure out where > rte > > comes from. > > Other than that , except for my own refactoring pains when replacing a > dpdk > > version, I do not see a major reason why not. > > If Going for dpdk_ prefix, I agree with the quick death approach. > > +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. > > And here are few more comments: > > - we should add rte_/dpdk_ prefix to all public structures as well. > > I'm thinking we are doing well here. I'm just aware that vhost lib > does a bad job, which is something I proposed to fix in next release. > > - If we do the whole change once, I'd suggest to do it ASAP when this > release is over. > > It should be a HUGE change that touches a lot of code, if we do it > later, at a stage that a lot of patches for new features have been > made or sent out, all of them need rebase. That'd be painful. > This last point that yliu brings up is the one that worries me. DPDK already has a serious problem with the patch backlog. It can take months for even small bug fixes to get merged. >>From the app side, it's not the end of the world if there is a one time, single shot change to the prefix. However, I'm not sure it's worth it because of the impact on patches that have been submitted. As others have mentioned, google can sort the rte_* references just fine. Jay