Re: [dpdk-dev] [PATCH] crypto/openssl: performance improvements

2017-08-16 Thread Akhil Goyal
Hi Pablo, On 8/15/2017 12:56 PM, De Lara Guarch, Pablo wrote: Hi, -Original Message- From: Akhil Goyal [mailto:akhil.go...@nxp.com] Sent: Tuesday, August 15, 2017 7:45 AM To: De Lara Guarch, Pablo ; dev@dpdk.org; Doherty, Declan Cc: hemant.agra...@nxp.com Subject: Re: [PATCH] crypto/op

Re: [dpdk-dev] [RFC PATCH 1/4] rte_security: API definitions

2017-08-16 Thread Akhil Goyal
On 8/15/2017 4:34 PM, Radu Nicolau wrote: On 8/15/2017 7:35 AM, Akhil Goyal wrote: Detailed description is added in the coverletter Signed-off-by: Akhil Goyal --- lib/librte_cryptodev/rte_security.c | 171 +++ lib/librte_cryptodev/rte_security.h | 409 +

Re: [dpdk-dev] [PATCH] net/failsafe: fix tx sub device deactivating

2017-08-16 Thread Gaëtan Rivet
Hi Matan, Thanks for spotting this, a few nits below. On Tue, Aug 15, 2017 at 09:59:19AM +0300, Matan Azrad wrote: > The corrupted code couldn't recognize that all sub devices > were not ready for tx traffic when failsafe PMD was trying > to switch device because of an unreachable condition using

Re: [dpdk-dev] [PATCH] net/failsafe: fix tx sub device deactivating

2017-08-16 Thread Matan Azrad
Hi Gaetan > -Original Message- > From: Gaëtan Rivet [mailto:gaetan.ri...@6wind.com] > Sent: Wednesday, August 16, 2017 11:47 AM > To: Matan Azrad > Cc: dev@dpdk.org; sta...@dpdk.org > Subject: Re: [PATCH] net/failsafe: fix tx sub device deactivating > > Hi Matan, > > Thanks for spotting

Re: [dpdk-dev] [PATCH] doc: add i40e firmware upgrade guide

2017-08-16 Thread Yang, Qiming
> -Original Message- > From: Yigit, Ferruh > Sent: Tuesday, August 15, 2017 4:52 PM > To: Yang, Qiming ; dev@dpdk.org > Cc: Wu, Jingjing ; Xing, Beilei > Subject: Re: [dpdk-dev] [PATCH] doc: add i40e firmware upgrade guide > > On 8/15/2017 4:26 AM, Qiming Yang wrote: > > This patch adds o

[dpdk-dev] [PATCH v3] cryptodev: allocate driver structure statically

2017-08-16 Thread Pablo de Lara
When register a crypto driver, a cryptodev driver structure was being allocated, using malloc. Since this call may fail, it is safer to allocate this memory statically in each PMD, so driver registration will never fail. Coverity issue: 158645 Fixes: 7a364faef185 ("cryptodev: remove crypto device

Re: [dpdk-dev] [PATCH 0/8] service: rework for usability

2017-08-16 Thread Neil Horman
On Tue, Aug 15, 2017 at 01:32:32PM +0100, Harry van Haaren wrote: > This patchset reworks the service apis to be more user > friendly. In particular, the various rte_service_* functions > now take an integer id parameter instead of a service pointer. > This both reduces the API surface (no service_

Re: [dpdk-dev] [PATCH 0/8] service: rework for usability

2017-08-16 Thread Van Haaren, Harry
> From: Neil Horman [mailto:nhor...@tuxdriver.com] > Sent: Wednesday, August 16, 2017 12:16 PM > To: Van Haaren, Harry > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH 0/8] service: rework for usability > > On Tue, Aug 15, 2017 at 01:32:32PM +0100, Harry van Haaren wrote: > > This patchset rew

[dpdk-dev] [PATCH] ethdev: fix device state on close

2017-08-16 Thread Shahaf Shuler
Currently device state moves between ATTACHED when device was successfully probed to UNUSED when device is detached or released. The device state following rte_eth_dev_close() operation is inconsist, The device is still in ATTACHED state, however it cannot be used in any way till it will be probed

Re: [dpdk-dev] [PATCH 0/8] service: rework for usability

2017-08-16 Thread Van Haaren, Harry
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Van Haaren, Harry > Sent: Wednesday, August 16, 2017 12:32 PM > To: Neil Horman > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH 0/8] service: rework for usability > > > From: Neil Horman [mailto:nhor...@tuxdriver.com] > > Sent: Wednesday,

Re: [dpdk-dev] [PATCH] ethdev: fix device state on close

2017-08-16 Thread Gaëtan Rivet
Hello Shahaf, On Wed, Aug 16, 2017 at 02:43:08PM +0300, Shahaf Shuler wrote: > Currently device state moves between ATTACHED when device was > successfully probed to UNUSED when device is detached or released. > > The device state following rte_eth_dev_close() operation is inconsist, > The device

Re: [dpdk-dev] [PATCH] net/failsafe: fix tx sub device deactivating

2017-08-16 Thread Gaëtan Rivet
On Wed, Aug 16, 2017 at 09:02:31AM +, Matan Azrad wrote: > Hi Gaetan > > > -Original Message- > > From: Gaëtan Rivet [mailto:gaetan.ri...@6wind.com] > > Sent: Wednesday, August 16, 2017 11:47 AM > > To: Matan Azrad > > Cc: dev@dpdk.org; sta...@dpdk.org > > Subject: Re: [PATCH] net/fai

Re: [dpdk-dev] [PATCH 0/8] service: rework for usability

2017-08-16 Thread Neil Horman
On Wed, Aug 16, 2017 at 12:07:11PM +, Van Haaren, Harry wrote: > > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Van Haaren, Harry > > Sent: Wednesday, August 16, 2017 12:32 PM > > To: Neil Horman > > Cc: dev@dpdk.org > > Subject: Re: [dpdk-dev] [PATCH 0/8] service: rework for usability

Re: [dpdk-dev] [PATCH] ethdev: fix device state on close

2017-08-16 Thread Shahaf Shuler
Wednesday, August 16, 2017 3:42 PM, Gaëtan Rivet: > On Wed, Aug 16, 2017 at 02:43:08PM +0300, Shahaf Shuler wrote: > > Currently device state moves between ATTACHED when device was > > successfully probed to UNUSED when device is detached or released. > > > > The device state following rte_eth_dev_

[dpdk-dev] [PATCH v2] net/failsafe: fix tx sub device deactivating

2017-08-16 Thread Matan Azrad
The corrupted code couldn't recognize that all sub devices were not ready for tx traffic when failsafe PMD was trying to switch device because of an unreachable condition using. Hence, the current tx sub device variable was not updated correctly. The fix removed the unreachable branch and added n

Re: [dpdk-dev] [PATCH v2] net/failsafe: fix tx sub device deactivating

2017-08-16 Thread Gaëtan Rivet
On Wed, Aug 16, 2017 at 05:19:28PM +0300, Matan Azrad wrote: > The corrupted code couldn't recognize that all sub devices > were not ready for tx traffic when failsafe PMD was trying > to switch device because of an unreachable condition using. > > Hence, the current tx sub device variable was not

Re: [dpdk-dev] [PATCH v2] net/failsafe: fix tx sub device deactivating

2017-08-16 Thread Matan Azrad
Hi > -Original Message- > From: Gaëtan Rivet [mailto:gaetan.ri...@6wind.com] > Sent: Wednesday, August 16, 2017 5:39 PM > To: Matan Azrad > Cc: dev@dpdk.org; sta...@dpdk.org > Subject: Re: [PATCH v2] net/failsafe: fix tx sub device deactivating > > On Wed, Aug 16, 2017 at 05:19:28PM +030

Re: [dpdk-dev] [PATCH] ethdev: fix device state on close

2017-08-16 Thread Gaëtan Rivet
On Wed, Aug 16, 2017 at 02:17:16PM +, Shahaf Shuler wrote: > Wednesday, August 16, 2017 3:42 PM, Gaëtan Rivet: > > On Wed, Aug 16, 2017 at 02:43:08PM +0300, Shahaf Shuler wrote: > > > Currently device state moves between ATTACHED when device was > > > successfully probed to UNUSED when device i

Re: [dpdk-dev] [RFC PATCH 1/4] rte_security: API definitions

2017-08-16 Thread Hemant Agrawal
Hi Thomas, Can we get a next-security tree to do development around this proposal? Also, we can discuss about this proposal in general in next techboard meeting. Regards, Hemant > -Original Message- > From: Akhil Goyal [mailto:akhil.go...@nxp.com] > Sent: Wednesday, Augu

Re: [dpdk-dev] [PATCH v6 08/12] linuxapp/eal: auto detect iova mode

2017-08-16 Thread Aaron Conole
Santosh Shukla writes: > - Moving late bus scanning to up..just after eal_parsing. > - Auto detect iova mapping mode, based on the result of > rte_bus_scan_iommu_class. > > Signed-off-by: Santosh Shukla > Signed-off-by: Jerin Jacob > Reviewed-by: Maxime Coquelin > --- > lib/librte_eal/linux

Re: [dpdk-dev] [PATCH] ethdev: fix device state on close

2017-08-16 Thread Shahaf Shuler
Wednesday, August 16, 2017 6:26 PM, Gaëtan Rivet: > > Even though it is reasonable for driver to call the > rte_eth_dev_port_release, I still think the ethdev layer should protect from > such bad behavior from the application side. > > It is more robust than counting on the different PMD to impleme

[dpdk-dev] [ovs-dpdk-tests] where is ovs-dpdk test case?

2017-08-16 Thread Sam
Hi all, I'm working with ovs-dpdk, I want to run ovs-dpdk test case. But I found there is no test case for 'netdev' type bridge and no test case for ovs-dpdk datapath(which is pmd_thread_main). So my question is where could I find these test cases? Also I change some code in dpdk-vhost client mo