Re: [dpdk-dev] [PATCH v2 36/38] doc: add OCTEONTX ssovf details

2017-04-02 Thread Jerin Jacob
On Sun, Apr 02, 2017 at 12:29:22PM +, Mcnamara, John wrote: > > > -Original Message- > > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Jerin Jacob > > Sent: Friday, March 31, 2017 8:35 PM > > To: dev@dpdk.org > > Cc: thomas.monja...@6wind.com; Richardson, Bruce > > ; Van Haaren,

[dpdk-dev] [PATCH ] doc: Fix a typo in a section about i40e PMD limitation.

2017-04-02 Thread Rami Rosen
This patch fixes a trivial typo in i40e documentation; commit edf1b ("add limitations for i40e PMD") added a comment about the behaviour upon DPDK application quit; however, it was wrongly titled as "after DPDK application exist" instead of "after DPDK application exit", and this trivial patch fix

Re: [dpdk-dev] [PATCH v2 36/38] doc: add OCTEONTX ssovf details

2017-04-02 Thread Mcnamara, John
> -Original Message- > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Jerin Jacob > Sent: Friday, March 31, 2017 8:35 PM > To: dev@dpdk.org > Cc: thomas.monja...@6wind.com; Richardson, Bruce > ; Van Haaren, Harry > ; hemant.agra...@nxp.com; Eads, Gage > ; nipun.gu...@nxp.com; > sant

Re: [dpdk-dev] [PATCH v2 7/7] net/enic: flow API documentation

2017-04-02 Thread Mcnamara, John
> -Original Message- > From: John Daley [mailto:johnd...@cisco.com] > Sent: Friday, March 31, 2017 3:06 AM > To: Yigit, Ferruh ; Mcnamara, John > > Cc: dev@dpdk.org; John Daley > Subject: [PATCH v2 7/7] net/enic: flow API documentation > > Update enic NIC guide, release notes and add f

Re: [dpdk-dev] [PATCH v7 17/22] test/eventdev: add SW tests for load balancing

2017-04-02 Thread Jerin Jacob
On Thu, Mar 30, 2017 at 08:30:45PM +0100, Harry van Haaren wrote: > This commit adds various tests for load-balancing and > queue prioritization. > > Signed-off-by: Bruce Richardson > Signed-off-by: David Hunt > Signed-off-by: Harry van Haaren > > Acked-by: Anatoly Burakov Hi Harry, I got

Re: [dpdk-dev] [PATCH v2 36/38] doc: add OCTEONTX ssovf details

2017-04-02 Thread Mcnamara, John
> -Original Message- > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Jerin Jacob > Sent: Friday, March 31, 2017 8:35 PM > To: dev@dpdk.org > Cc: thomas.monja...@6wind.com; Richardson, Bruce > ; Van Haaren, Harry > ; hemant.agra...@nxp.com; Eads, Gage > ; nipun.gu...@nxp.com; > santo

Re: [dpdk-dev] [PATCH v2 38/38] doc: add Cavium OCTEONTX eventdev PMD to 17.05 release notes

2017-04-02 Thread Mcnamara, John
> -Original Message- > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Jerin Jacob > Sent: Friday, March 31, 2017 8:35 PM > To: dev@dpdk.org > Cc: thomas.monja...@6wind.com; Richardson, Bruce > ; Van Haaren, Harry > ; hemant.agra...@nxp.com; Eads, Gage > ; nipun.gu...@nxp.com; > sant

Re: [dpdk-dev] [RFC 2/2] doc: include PMD build and run file in liquidio doc

2017-04-02 Thread Mcnamara, John
> -Original Message- > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Shijith Thotton > Sent: Saturday, April 1, 2017 4:04 PM > To: dev@dpdk.org > Cc: Yigit, Ferruh > Subject: [dpdk-dev] [RFC 2/2] doc: include PMD build and run file in > liquidio doc > > Include build_and_run.inc

Re: [dpdk-dev] [RFC 1/2] doc: add doc with steps to build PMD and run testpmd

2017-04-02 Thread Mcnamara, John
> -Original Message- > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Mcnamara, John > Sent: Sunday, April 2, 2017 1:11 PM > To: Shijith Thotton ; dev@dpdk.org > Cc: Yigit, Ferruh > Subject: Re: [dpdk-dev] [RFC 1/2] doc: add doc with steps to build PMD and > run testpmd > > > >

Re: [dpdk-dev] [RFC 1/2] doc: add doc with steps to build PMD and run testpmd

2017-04-02 Thread Mcnamara, John
> -Original Message- > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Shijith Thotton > Sent: Saturday, April 1, 2017 4:04 PM > To: dev@dpdk.org > Cc: Yigit, Ferruh > Subject: [dpdk-dev] [RFC 1/2] doc: add doc with steps to build PMD and run > testpmd > > Add a new document with s

Re: [dpdk-dev] [PATCH] doc: fix description on intel VFs

2017-04-02 Thread Mcnamara, John
> -Original Message- > From: Wu, Jingjing > Sent: Sunday, April 2, 2017 1:24 AM > To: Mcnamara, John > Cc: dev@dpdk.org; Wu, Jingjing ; sta...@dpdk.org > Subject: [PATCH] doc: fix description on intel VFs > > This patch corrects the description on Physical and Virtual Function > Infrast

[dpdk-dev] [PATCH v2] net/mlx5: remove unnecessary Verbs library calls

2017-04-02 Thread Shahaf Shuler
Remove unnecessary interface queries and the Resource Domain when creating the Queue Pair. Since mlx5 PMD data path is on top of native APIs, such Verbs library calls are no longer needed. Signed-off-by: Shahaf Shuler Acked-by: Nelio Laranjeiro Acked-by: Yongseok Koh --- on v2: * clarify commi

[dpdk-dev] [PATCH v5 3/3] app/testpmd: add CL for ptype mapping configure

2017-04-02 Thread Qi Zhang
Add below command line to configure ptype mapping. ptype mapping get . ptype mapping replace. ptype mapping reset . ptype mapping update . Signed-off-by: Qi Zhang --- v5: - Rebase to dpdk-next-net v3: - Fix compile issue when CONFIG_RTE_LIBRTE_I40E_PMD=n app/test-pmd/cmdline.c | 372 +

[dpdk-dev] [PATCH v5 2/3] net/i40e: configurable PTYPE mapping

2017-04-02 Thread Qi Zhang
The patch adds 4 APIs to support configurable PTYPE mapping for i40e device. rte_pmd_i40e_ptype_mapping_get. rte_pmd_i40e_ptype_mapping_replace. rte_pmd_i40e_ptype_mapping_reset. rte_pmd_i40e_ptype_mapping_update. The mapping from hardware defined packet type to software defined packet type can be

[dpdk-dev] [PATCH v5 1/3] net/i40e: enable per dev PTYPE mapping table

2017-04-02 Thread Qi Zhang
The mapping from hardware defined packet type to software defined packet type is static for i40e device, the patch let each ethdev to to have their own copy of mapping table, this give the possibility that different ethdev can be set different PTYPE mapping rule which is the requirement to support

[dpdk-dev] [PATCH v5 0/3] net/i40e: configurable PTYPE mapping

2017-04-02 Thread Qi Zhang
The patch set create new APIs that help to change the mapping from hardware defined packet type to software defined packet type for i40e NICs. Keep these APIs private is because currently they are only meaningful for devices that support dynamic PTYPE configuration, which may not be a general devic