From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id A8236ADE6 for ; Wed, 8 Jun 2016 15:17:47 +0200 (CEST) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga103.fm.intel.com with ESMTP; 08 Jun 2016 06:15:20 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.26,439,1459839600"; d="scan'208";a="824129178" Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.237.221.53]) ([10.237.221.53]) by orsmga003.jf.intel.com with ESMTP; 08 Jun 2016 06:15:19 -0700 To: Jerin Jacob References: <1464540424-12631-1-git-send-email-jerin.jacob@caviumnetworks.com> <1465317632-11471-1-git-send-email-jerin.jacob@caviumnetworks.com> <57580FE4.3060808@intel.com> <20160608124319.GA4449@localhost.localdomain> Cc: dev@dpdk.org, thomas.monjalon@6wind.com, bruce.richardson@intel.com From: Ferruh Yigit Message-ID: <57581A66.2080409@intel.com> Date: Wed, 8 Jun 2016 14:15:18 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <20160608124319.GA4449@localhost.localdomain> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-dev] [PATCH v3 00/20] DPDK PMD for ThunderX NIC device 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, 08 Jun 2016 13:17:48 -0000 On 6/8/2016 1:43 PM, Jerin Jacob wrote: > On Wed, Jun 08, 2016 at 01:30:28PM +0100, Ferruh Yigit wrote: >> On 6/7/2016 5:40 PM, Jerin Jacob wrote: >>> Jerin Jacob (20): >>> thunderx/nicvf/base: add hardware API for ThunderX nicvf inbuilt NIC >>> thunderx/nicvf: add pmd skeleton >>> thunderx/nicvf: add link status and link update support >>> thunderx/nicvf: add get_reg and get_reg_length support >>> thunderx/nicvf: add dev_configure support >>> thunderx/nicvf: add dev_infos_get support >>> thunderx/nicvf: add rx_queue_setup/release support >>> thunderx/nicvf: add tx_queue_setup/release support >>> thunderx/nicvf: add rss and reta query and update support >>> thunderx/nicvf: add mtu_set and promiscuous_enable support >>> thunderx/nicvf: add stats support >>> thunderx/nicvf: add single and multi segment tx functions >>> thunderx/nicvf: add single and multi segment rx functions >>> thunderx/nicvf: add dev_supported_ptypes_get and rx_queue_count >>> support >>> thunderx/nicvf: add rx queue start and stop support >>> thunderx/nicvf: add tx queue start and stop support >>> thunderx/nicvf: add device start,stop and close support >>> thunderx/config: set max numa node to two >>> thunderx/nicvf: updated driver documentation and release notes >>> maintainers: claim responsibility for the ThunderX nicvf PMD >>> >> >> Hi Jerin, >> >> In patch subject, as tag, other drivers are using only driver name, and >> Intel drivers also has "driver/base", since base code has some special >> case. For thunderx, what do you think about keeping subject as: >> "thunderx: ...." >> > > Hi Ferruh, > > We may add crypto or other builtin ThunderX HW accelerated block drivers > in future to DPDK. > So that is the reason why I thought of keeping the subject as thunderx/nicvf. > If you don't have any objection then I would like to keep it as > thunderx/nicvf or just nicvf. > Ring has similar problem, but we are using same tag "ring:" for both ring_pmd and ring library. For this case perhaps we can use net/thunderx, crypto/thunderx ? I am not aware of any defined convention for the case. Thanks, ferruh