From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id A1FC0ADC2 for ; Wed, 8 Jun 2016 15:23:56 +0200 (CEST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga101.fm.intel.com with ESMTP; 08 Jun 2016 06:22:58 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.26,439,1459839600"; d="scan'208";a="993532839" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.220.95]) by orsmga002.jf.intel.com with SMTP; 08 Jun 2016 06:22:55 -0700 Received: by (sSMTP sendmail emulation); Wed, 08 Jun 2016 14:22:55 +0025 Date: Wed, 8 Jun 2016 14:22:55 +0100 From: Bruce Richardson To: Jerin Jacob Cc: Ferruh Yigit , dev@dpdk.org, thomas.monjalon@6wind.com Message-ID: <20160608132254.GC24744@bricha3-MOBL3> 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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160608124319.GA4449@localhost.localdomain> Organization: Intel Research and =?iso-8859-1?Q?De=ACvel?= =?iso-8859-1?Q?opment?= Ireland Ltd. User-Agent: Mutt/1.5.23 (2014-03-12) 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:23:57 -0000 On Wed, Jun 08, 2016 at 06:13:21PM +0530, 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. Are you upstreaming kernel modules for this device? If so, what is the Linux kernel module-name for this device going to be, as perhaps that can help us here? Regards, /Bruce