From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH v3 00/20] DPDK PMD for ThunderX NIC device Date: Wed, 8 Jun 2016 13:30:28 +0100 Message-ID: <57580FE4.3060808@intel.com> References: <1464540424-12631-1-git-send-email-jerin.jacob@caviumnetworks.com> <1465317632-11471-1-git-send-email-jerin.jacob@caviumnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: thomas.monjalon@6wind.com, bruce.richardson@intel.com To: Jerin Jacob , dev@dpdk.org Return-path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 6F4FEADCA for ; Wed, 8 Jun 2016 14:30:31 +0200 (CEST) In-Reply-To: <1465317632-11471-1-git-send-email-jerin.jacob@caviumnetworks.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 6/7/2016 5:40 PM, Jerin Jacob wrote: > This patch set provides the initial version of DPDK PMD for the > built-in NIC device in Cavium ThunderX SoC family. > > Implemented features and ThunderX nicvf PMD documentation added > in doc/guides/nics/overview.rst and doc/guides/nics/thunderx.rst > respectively in this patch set. > > These patches are checked using checkpatch.sh with following > additional ignore option: > options="$options --ignore=CAMELCASE,BRACKET_SPACE" > CAMELCASE - To accommodate PRIx64 > BRACKET_SPACE - To accommodate AT&T inline line assembly in two places > > This patch set is based on DPDK 16.07-RC1 > and tested with today's git HEAD change-set > ca173a909538a2f1082cd0dcb4d778a97dab69c3 along with > following depended patch > > http://dpdk.org/dev/patchwork/patch/11826/ > ethdev: add tunnel and port RSS offload types > > V1->V2 > > http://dpdk.org/dev/patchwork/patch/12609/ > -- added const for the const struct tables > -- remove multiple blank lines > -- addressed style comments > http://dpdk.org/dev/patchwork/patch/12610/ > -- removed DEPDIRS-$(CONFIG_RTE_LIBRTE_THUNDERX_NICVF_PMD) += lib/librte_net lib/librte_malloc > -- add const for table structs > -- addressed style comments > http://dpdk.org/dev/patchwork/patch/12614/ > -- s/DEFAULT_*/NICVF_DEFAULT_*/gc > http://dpdk.org/dev/patchwork/patch/12615/ > -- Fix typos > -- addressed style comments > http://dpdk.org/dev/patchwork/patch/12616/ > -- removed redundant txq->tail = 0 and txq->head = 0 > http://dpdk.org/dev/patchwork/patch/12627/ > -- fixed the documentation changes > > -- fixed TAB+space occurrences in functions > -- rebased to c8c33ad7f94c59d1c0676af0cfd61207b3e808db > > V2->V3 > > http://dpdk.org/dev/patchwork/patch/13060/ > -- Changed polling infrastructure to use rte_eal_alarm* instead of timerfd_create API > -- rebased to ca173a909538a2f1082cd0dcb4d778a97dab69c3 > > 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: ...." Thanks, ferruh