From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f44.google.com (mail-wm0-f44.google.com [74.125.82.44]) by dpdk.org (Postfix) with ESMTP id EF3122931 for ; Mon, 11 Apr 2016 18:28:36 +0200 (CEST) Received: by mail-wm0-f44.google.com with SMTP id v188so93566186wme.1 for ; Mon, 11 Apr 2016 09:28:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:organization:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=H4kqZOWoJwg2ELDNSczeuBgaBU3M/Zp3zn+BjRN/cX0=; b=V+dKfVLVujJ0eXjCUD222g8uJfWoVqBmNlMLVv2VWEsODbl2wBNxE2mpQV6Q2+kR0p Ygt7J1mBboBRpcin4NwKeVfM6v3e5K6KS1BARRRas+dz+r6w1BDNEzYUW+8hKASJ+vfN HU/AK2DTTxAUgVMaGqV1O4f8ffTVl5R1J+cUHOlavUqGOeVFdCE+VdkS/LA+CVzTZPuy MMpjx8/rCou9Sn+gPyzv9plMwVHIBWJCSdGfjmDSmGriiC4/70f8h0P+Nh6MfsgEUBa7 lenzkquei75xogGnc4AlUlsToTkWjoKCL1SylfusvBXgIAhQN5NSu6t9XUf34w9iYsht pjSA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:organization :user-agent:in-reply-to:references:mime-version :content-transfer-encoding; bh=H4kqZOWoJwg2ELDNSczeuBgaBU3M/Zp3zn+BjRN/cX0=; b=XALCBL5rltzuEmKUnreB8lVejCcAjMvao5c6jQ7oGeDWmK9dYzL7gcdqKx2IFlTubh cu1rB/mRVXg/xr/nVbUTOqzcmb5KOGOex72id0p8qBOsxN+9BUCPr+U88mbNeDaywhBQ HSH+heIzXsgalR28g1kAExlbNPqEvFtui7WF39lTi6gDaq2v0I6+1ROPt6VR7Ul6lCxc bPNcelvpw1ql/M4GZa2AiUItFrzMU2pMBdxCpPrKvj5GHDEfm++jkrVg+79KEWbfGhiV RqUShL4Ym6kWXPExXKYOUsY17kL0wuLoBQaAYC7Cl37ZDoASV+xxNNVMJLDcjDcyLp9h lCGw== X-Gm-Message-State: AD7BkJIgBAtkon8e5TWmaxilYeobn3mTiIP/uOWYiEKqlC+UTx6rrCZXR6A0tTvE/kCqvN1V X-Received: by 10.28.175.201 with SMTP id y192mr20124721wme.54.1460392116644; Mon, 11 Apr 2016 09:28:36 -0700 (PDT) Received: from xps13.localnet (245.111.75.86.rev.sfr.net. [86.75.111.245]) by smtp.gmail.com with ESMTPSA id r204sm2489869wmg.20.2016.04.11.09.28.35 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 11 Apr 2016 09:28:35 -0700 (PDT) From: Thomas Monjalon To: Don Provan Cc: dev@dpdk.org Date: Mon, 11 Apr 2016 18:28:34 +0200 Message-ID: <7302895.X0llXgHgZ1@xps13> Organization: 6WIND User-Agent: KMail/4.14.10 (Linux/4.1.6-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: References: <1610488.T03Kyi0Reo@xps13> <5704FC10.8020405@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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: Mon, 11 Apr 2016 16:28:37 -0000 2016-04-11 16:10, Don Provan: > I can't believe you guys are seriously considering changing the prefix from rte_. That's a nightmare at the practical level, but it really doesn't make as much sense as some of you seem to think. I've always been really impressed that the names were prefixed with rte_ instead of dpdk_. While the primary goal was to provide dataplane capabilities, so much of the library -- mempools and rings, for example -- is general purpose, so a dpdk_ prefix wouldn't be appropriate for those routines, anyway. > > The idea that everything in the library should be named "dpdk" is the same thinking that leads to the monolithic initialization function I've complained about before. I have major applications that use the DPDK library but do nothing at all with hardware, yet the library still insists on initializing the PCI components because there's no concept of using the library for anything other than receiving packets from hardware. It's good news to hear that DPDK allows you to develop major applications. The BSD license allows to build a lot of various types of applications. You are perfectly right to give your opinion and complain. You would also be welcome to contribute and fix your concerns.