From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Subject: Re: [PATCH v3 00/20] DPDK PMD for ThunderX NIC device
Date: Wed, 8 Jun 2016 19:02:55 +0530
Message-ID: <20160608133253.GA6248@localhost.localdomain>
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>
 <20160608132254.GC24744@bricha3-MOBL3>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: Ferruh Yigit <ferruh.yigit@intel.com>, <dev@dpdk.org>,
 <thomas.monjalon@6wind.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from na01-by2-obe.outbound.protection.outlook.com
 (mail-by2on0090.outbound.protection.outlook.com [207.46.100.90])
 by dpdk.org (Postfix) with ESMTP id 7EC6D5A31
 for <dev@dpdk.org>; Wed,  8 Jun 2016 15:33:20 +0200 (CEST)
Content-Disposition: inline
In-Reply-To: <20160608132254.GC24744@bricha3-MOBL3>
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

On Wed, Jun 08, 2016 at 02:22:55PM +0100, Bruce Richardson wrote:
> 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?

Yes, Kernel module has been upstreamed.
the commit log in linux kernel is "net: thunderx: ......."

> 
> Regards,
> /Bruce