Re: [dpdk-dev] [RFC PATCH] eventdev: add buffered enqueue and flush APIs

On Mon, Dec 12, 2016 at 05:56:32PM +, Eads, Gage wrote: > > > > -Original Message- > > From: Jerin Jacob [mailto:jerin.ja...@caviumnetworks.com] > > Sent: Wednesday, December 7, 2016 10:42 PM > > To: Eads, Gage > > Cc: dev@dpdk.org; Richardson, Bruce ; Van > > Haaren, Harry ; h

Re: [dpdk-dev] [RFC PATCH] eventdev: add buffered enqueue and flush APIs

On Mon, Dec 12, 2016 at 05:56:32PM +, Eads, Gage wrote: > > > > -Original Message- > > From: Jerin Jacob [mailto:jerin.ja...@caviumnetworks.com] > > Sent: Wednesday, December 7, 2016 10:42 PM > > To: Eads, Gage > > 1) What if the burst has ATOMIC flows and if we are NOT en-queui

Re: [dpdk-dev] [PATCH 5/5] net/virtio: fix Tso when mbuf is shared

Hi Olivier, Firstly sorry for late response! On Thu, Nov 24, 2016 at 09:56:38AM +0100, Olivier Matz wrote: > With virtio, doing tso requires to modify the network > packet data: I thought more about it this time, and I'm wondering why it's needed. > - the dpdk API requires to set the l4 checksu

Re: [dpdk-dev] [PATCH v3] net/ixgbe:fix max packet length in ixgbevf

On Thu, Dec 15, 2016 at 02:50:19AM +0800, Yi Zhang wrote: > Current ixgbevf driver get max_rx_pktlen = 15872, but in fact PF > supports 15872-byte jumbo frame and VF only supports 9728-byte jumbo > frame. If VF is running DPDK driver and set frame_size > 9728 ,PF > running kernel ixgbe driver will

Re: [dpdk-dev] [PATCH v2 1/6] eventdev: introduce event driven programming model

On Fri, Dec 09, 2016 at 03:11:42PM +, Bruce Richardson wrote: > On Fri, Dec 09, 2016 at 02:11:15AM +0530, Jerin Jacob wrote: > > On Thu, Dec 08, 2016 at 09:30:49AM +, Bruce Richardson wrote: > > > On Thu, Dec 08, 2016 at 12:23:03AM +0530, Jerin Jacob wrote: > > > > On Tue, Dec 06, 2016 at 0

Re: [dpdk-dev] [PATCH v2 1/6] eventdev: introduce event driven programming model

On Thu, Dec 08, 2016 at 09:57:52AM +, Bruce Richardson wrote: > On Thu, Dec 08, 2016 at 07:18:01AM +0530, Jerin Jacob wrote: > > On Wed, Dec 07, 2016 at 11:12:51AM +, Bruce Richardson wrote: > > > On Tue, Dec 06, 2016 at 09:22:15AM +0530, Jerin Jacob wrote: > > > > + */ > > > > +int > > > >

[dpdk-dev] [PATCH v3] net/ixgbe:fix max packet length in ixgbevf

Current ixgbevf driver get max_rx_pktlen = 15872, but in fact PF supports 15872-byte jumbo frame and VF only supports 9728-byte jumbo frame. If VF is running DPDK driver and set frame_size > 9728 ,PF running kernel ixgbe driver will report an error and set VF failed. This patch fixs DPDK ixgbevf dr

Re: [dpdk-dev] [PATCH v2 3/6] eventdev: implement the northbound APIs

On Thu, Dec 08, 2016 at 09:59:37AM +, Bruce Richardson wrote: > On Wed, Dec 07, 2016 at 10:32:56PM +0530, Jerin Jacob wrote: > > On Tue, Dec 06, 2016 at 05:17:12PM +, Bruce Richardson wrote: > > > On Tue, Dec 06, 2016 at 09:22:17AM +0530, Jerin Jacob wrote: > > > > This patch implements nor

Re: [dpdk-dev] [PATCH v2 12/12] drivers: update PMDs to use rte_driver probe and remove

Hello Ferruh, On Tuesday 13 December 2016 08:37 PM, Ferruh Yigit wrote: On 12/13/2016 1:52 PM, Andrew Rybchenko wrote: On 12/13/2016 04:37 PM, Shreyansh Jain wrote: These callbacks now act as first layer of PCI interfaces from the Bus. Bus probe would enter the PMDs through the rte_driver->pro

Re: [dpdk-dev] [PATCH v2 01/12] eal: define container_of macro

On Wednesday 14 December 2016 03:54 AM, Jan Blunck wrote: On Tue, Dec 13, 2016 at 2:37 PM, Shreyansh Jain wrote: From: Jan Blunck This macro is based on Jan Viktorin's original patch but also checks the type of the passed pointer against the type of the member. Signed-off-by: Jan Viktorin [

Re: [dpdk-dev] [PATCH v2 12/12] drivers: update PMDs to use rte_driver probe and remove

On Tuesday 13 December 2016 07:22 PM, Andrew Rybchenko wrote: On 12/13/2016 04:37 PM, Shreyansh Jain wrote: These callbacks now act as first layer of PCI interfaces from the Bus. Bus probe would enter the PMDs through the rte_driver->probe/remove callbacks, falling to rte_xxx_driver->probe/remov

Re: [dpdk-dev] [PATCH v4] vhost: allow for many vhost user ports

On Tue, Dec 13, 2016 at 02:19:47PM +0100, Jan Wickbom wrote: > + > + poll(pfdset->rwfds, numfds, 1000 /* millisecs */); > + > + for (i = 0; i < numfds; ) { > pthread_mutex_lock(&pfdset->fd_mutex); > + > pfdentry = &pfdset->fd[i]; >

Re: [dpdk-dev] [PATCH 26/28] net/virtio: use eal I/O device memory read/write API

On Wed, Dec 14, 2016 at 07:25:56AM +0530, Jerin Jacob wrote: > * Following macros are derived from linux/pci_regs.h, however, > * we can't simply include that header here, as there is no such > @@ -320,37 +322,37 @@ static const struct virtio_pci_ops legacy_ops = { > static inline uint8_t > i

Re: [dpdk-dev] [PATCH 27/28] net/vmxnet3: use eal I/O device memory read/write API

On Wed, Dec 14, 2016 at 07:25:57AM +0530, Jerin Jacob wrote: > From: Santosh Shukla > > Replace the raw I/O device memory read/write access with eal > abstraction for I/O device memory read/write access to fix > portability issues across different architectures. > > Signed-off-by: Santosh Shukla

Re: [dpdk-dev] [PATCH 00/28] introduce I/O device memory read/write operations

On Wed, Dec 14, 2016 at 07:25:30AM +0530, Jerin Jacob wrote: > patchset 14-28: Replace the raw readl/writel in the drivers with > new rte_read[b/w/l/q], rte_write[b/w/l/q] eal abstraction Instead of rte_read[b/w/l/q], there is another typical naming style: rte_read[8/16/32/64]. Any preferences? If

Re: [dpdk-dev] [PATCH 26/28] net/virtio: use eal I/O device memory read/write API

On Wed, Dec 14, 2016 at 07:25:56AM +0530, Jerin Jacob wrote: > From: Santosh Shukla > > Replace the raw I/O device memory read/write access with eal > abstraction for I/O device memory read/write access to fix > portability issues across different architectures. I think these APIs are good: Ack

Re: [dpdk-dev] [PATCH 04/13] acl: allow zero verdict

On Tue, Dec 13, 2016 at 09:55:12PM +, Ananyev, Konstantin wrote: > > > > -Original Message- > > From: Michal Miroslaw [mailto:mirq-li...@rere.qmqm.pl] > > Sent: Tuesday, December 13, 2016 6:03 PM > > To: Ananyev, Konstantin > > Cc: dev@dpdk.org > > Subject: Re: [dpdk-dev] [PATCH 04/1

Re: [dpdk-dev] [PATCH 02/13] mbuf: rte_pktmbuf_free_bulk()

On Tue, Dec 13, 2016 at 01:41:11PM -0800, Stephen Hemminger wrote: > On Tue, 13 Dec 2016 02:08:15 +0100 (CET) > Michał Mirosław wrote: > > > Signed-off-by: Michał Mirosław > > > > --- > > lib/librte_mbuf/rte_mbuf.h | 15 +++ > > 1 file changed, 15 insertions(+) > > > > diff --git

[dpdk-dev] [PATCH 28/28] net/thunderx: use eal I/O device memory read/write API

Replace the raw I/O device memory read/write access with eal abstraction for I/O device memory read/write access to fix portability issues across different architectures. Signed-off-by: Jerin Jacob --- drivers/net/thunderx/base/nicvf_plat.h | 45 ++ 1 file changed

[dpdk-dev] [PATCH 27/28] net/vmxnet3: use eal I/O device memory read/write API

From: Santosh Shukla Replace the raw I/O device memory read/write access with eal abstraction for I/O device memory read/write access to fix portability issues across different architectures. Signed-off-by: Santosh Shukla Signed-off-by: Jerin Jacob CC: Yong Wang --- drivers/net/vmxnet3/vmxne

[dpdk-dev] [PATCH 25/28] net/qede: use eal I/O device memory read/write API

From: Santosh Shukla Replace the raw I/O device memory read/write access with eal abstraction for I/O device memory read/write access to fix portability issues across different architectures. Signed-off-by: Santosh Shukla Signed-off-by: Jerin Jacob CC: Harish Patil CC: Rasesh Mody --- drive

[dpdk-dev] [PATCH 26/28] net/virtio: use eal I/O device memory read/write API

From: Santosh Shukla Replace the raw I/O device memory read/write access with eal abstraction for I/O device memory read/write access to fix portability issues across different architectures. Signed-off-by: Santosh Shukla Signed-off-by: Jerin Jacob CC: Huawei Xie CC: Yuanhan Liu --- drivers

[dpdk-dev] [PATCH 24/28] net/nfp: use eal I/O device memory read/write API

From: Santosh Shukla Replace the raw I/O device memory read/write access with eal abstraction for I/O device memory read/write access to fix portability issues across different architectures. Signed-off-by: Santosh Shukla Signed-off-by: Jerin Jacob CC: Alejandro Lucero --- drivers/net/nfp/nf

[dpdk-dev] [PATCH 22/28] net/i40e: use eal I/O device memory read/write API

From: Santosh Shukla Replace the raw I/O device memory read/write access with eal abstraction for I/O device memory read/write access to fix portability issues across different architectures. Signed-off-by: Santosh Shukla Signed-off-by: Satha Rao Signed-off-by: Jerin Jacob CC: Helin Zhang CC

[dpdk-dev] [PATCH 23/28] net/ixgbe: use eal I/O device memory read/write API

From: Santosh Shukla Replace the raw I/O device memory read/write access with eal abstraction for I/O device memory read/write access to fix portability issues across different architectures. Signed-off-by: Santosh Shukla Signed-off-by: Jerin Jacob CC: Helin Zhang CC: Konstantin Ananyev ---

[dpdk-dev] [PATCH 21/28] net/fm10k: use eal I/O device memory read/write API

From: Santosh Shukla Replace the raw I/O device memory read/write access with eal abstraction for I/O device memory read/write access to fix portability issues across different architectures. Signed-off-by: Santosh Shukla Signed-off-by: Jerin Jacob CC: Jing Chen --- drivers/net/fm10k/base/fm

[dpdk-dev] [PATCH 20/28] net/enic: use eal I/O device memory read/write API

From: Santosh Shukla Replace the raw I/O device memory read/write access with eal abstraction for I/O device memory read/write access to fix portability issues across different architectures. Signed-off-by: Santosh Shukla Signed-off-by: Jerin Jacob CC: John Daley CC: Nelson Escobar --- driv

[dpdk-dev] [PATCH 19/28] net/ena: use eal I/O device memory read/write API

From: Santosh Shukla Replace the raw I/O device memory read/write access with eal abstraction for I/O device memory read/write access to fix portability issues across different architectures. Signed-off-by: Santosh Shukla Signed-off-by: Jerin Jacob CC: Jan Medala CC: Jakub Palider --- drive

[dpdk-dev] [PATCH 18/28] net/e1000: use eal I/O device memory read/write API

From: Santosh Shukla Replace the raw I/O device memory read/write access with eal abstraction for I/O device memory read/write access to fix portability issues across different architectures. Signed-off-by: Santosh Shukla Signed-off-by: Jerin Jacob CC: Wenzhuo Lu --- drivers/net/e1000/base/e

[dpdk-dev] [PATCH 17/28] net/cxgbe: use eal I/O device memory read/write API

From: Santosh Shukla Replace the raw I/O device memory read/write access with eal abstraction for I/O device memory read/write access to fix portability issues across different architectures. Signed-off-by: Santosh Shukla Signed-off-by: Jerin Jacob CC: Rahul Lakkireddy --- drivers/net/cxgbe/

[dpdk-dev] [PATCH 15/28] net/bnx2x: use eal I/O device memory read/write API

From: Santosh Shukla Replace the raw I/O device memory read/write access with eal abstraction for I/O device memory read/write access to fix portability issues across different architectures. Signed-off-by: Santosh Shukla Signed-off-by: Jerin Jacob CC: Harish Patil CC: Rasesh Mody --- drive

[dpdk-dev] [PATCH 14/28] crypto/qat: use eal I/O device memory read/write API

From: Santosh Shukla Replace the raw I/O device memory read/write access with eal abstraction for I/O device memory read/write access to fix portability issues across different architectures. Signed-off-by: Santosh Shukla Signed-off-by: Jerin Jacob CC: John Griffin CC: Fiona Trahe CC: Deepak

[dpdk-dev] [PATCH 16/28] net/bnxt: use eal I/O device memory read/write API

From: Santosh Shukla Replace the raw I/O device memory read/write access with eal abstraction for I/O device memory read/write access to fix portability issues across different architectures. Signed-off-by: Santosh Shukla Signed-off-by: Jerin Jacob CC: Stephen Hurd CC: Ajit Khaparde --- dri

[dpdk-dev] [PATCH 12/28] eal: let all architectures use generic I/O implementation

Signed-off-by: Jerin Jacob --- lib/librte_eal/common/include/arch/arm/rte_io.h| 47 ++ lib/librte_eal/common/include/arch/ppc_64/rte_io.h | 47 ++ lib/librte_eal/common/include/arch/tile/rte_io.h | 47 ++ lib/librte_eal/common/incl

[dpdk-dev] [PATCH 13/28] eal/arm64: override I/O device read/write access for arm64

Override the generic I/O device memory read/write access and implement it using armv8 instructions for arm64. Signed-off-by: Jerin Jacob --- lib/librte_eal/common/include/arch/arm/rte_io.h| 4 + lib/librte_eal/common/include/arch/arm/rte_io_64.h | 183 + 2 files changed

[dpdk-dev] [PATCH 11/28] eal: generic implementation for I/O device read/write access

This patch implements the generic version of rte_read[b/w/l/q]_[relaxed] and rte_write[b/w/l/q]_[relaxed] using rte_io_wmb() and rte_io_rmb() Signed-off-by: Jerin Jacob --- lib/librte_eal/common/include/generic/rte_io.h | 54 ++ 1 file changed, 54 insertions(+) diff --gi

[dpdk-dev] [PATCH 10/28] eal: introduce I/O device memory read/write operations

This commit introduces 8-bit, 16-bit, 32bit, 64bit I/O device memory read/write operations along with the relaxed versions. The weakly-ordered machine like ARM needs additional I/O barrier for device memory read/write access over PCI bus. By introducing the eal abstraction for I/O device memory re

[dpdk-dev] [PATCH 09/28] eal/arm64: define I/O device memory barriers for arm64

Signed-off-by: Jerin Jacob CC: Jianbo Liu --- lib/librte_eal/common/include/arch/arm/rte_atomic_64.h | 6 ++ 1 file changed, 6 insertions(+) diff --git a/lib/librte_eal/common/include/arch/arm/rte_atomic_64.h b/lib/librte_eal/common/include/arch/arm/rte_atomic_64.h index 78ebea2..ef0efc7 1

[dpdk-dev] [PATCH 08/28] eal/arm64: define smp barrier definition for arm64

dmb instruction based barrier is used for smp version of memory barrier. Signed-off-by: Jerin Jacob --- lib/librte_eal/common/include/arch/arm/rte_atomic_64.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/lib/librte_eal/common/include/arch/arm/rte_atomic_64.h b/lib/l

[dpdk-dev] [PATCH 07/28] eal/arm64: fix memory barrier definition for arm64

dsb instruction based barrier is used for non smp version of memory barrier. Fixes: d708f01b7102 ("eal/arm: add atomic operations for ARMv8") Signed-off-by: Jerin Jacob CC: Jianbo Liu CC: sta...@dpdk.org --- lib/librte_eal/common/include/arch/arm/rte_atomic_64.h | 9 + 1 file changed,

[dpdk-dev] [PATCH 06/28] eal/armv7: define I/O device memory barriers for ARMv7

The patch does not provide any functional change for ARMv7. I/O barriers are mapped to existing smp barriers. Signed-off-by: Jerin Jacob CC: Jan Viktorin CC: Jianbo Liu --- lib/librte_eal/common/include/arch/arm/rte_atomic_32.h | 6 ++ 1 file changed, 6 insertions(+) diff --git a/lib/libr

[dpdk-dev] [PATCH 04/28] eal/ppc64: define I/O device memory barriers for ppc64

The patch does not provide any functional change for ppc_64. I/O barriers are mapped to existing smp barriers. Signed-off-by: Jerin Jacob CC: Chao Zhu --- lib/librte_eal/common/include/arch/ppc_64/rte_atomic.h | 6 ++ 1 file changed, 6 insertions(+) diff --git a/lib/librte_eal/common/inclu

[dpdk-dev] [PATCH 03/28] eal/tile: define I/O device memory barriers for tile

The patch does not provide any functional change for tile. I/O barriers are mapped to existing smp barriers. Signed-off-by: Jerin Jacob CC: Zhigang Lu --- lib/librte_eal/common/include/arch/tile/rte_atomic.h | 6 ++ 1 file changed, 6 insertions(+) diff --git a/lib/librte_eal/common/include

[dpdk-dev] [PATCH 02/28] eal/x86: define I/O device memory barriers for IA

The patch does not provide any functional change for IA. I/O barriers are mapped to existing smp barriers. Signed-off-by: Jerin Jacob CC: Bruce Richardson CC: Konstantin Ananyev --- lib/librte_eal/common/include/arch/x86/rte_atomic.h | 6 ++ 1 file changed, 6 insertions(+) diff --git a/li

[dpdk-dev] [PATCH 05/28] eal/arm: separate smp barrier definition for ARMv7 and ARMv8

Separate the smp barrier definition for arm and arm64 for fine control on smp barrier definition for each architecture. Signed-off-by: Jerin Jacob --- lib/librte_eal/common/include/arch/arm/rte_atomic.h| 6 -- lib/librte_eal/common/include/arch/arm/rte_atomic_32.h | 6 ++ lib/librte_

[dpdk-dev] [PATCH 00/28] introduce I/O device memory read/write operations

Based on the disussion in the below-mentioned thread, http://dev.dpdk.narkive.com/DpIRqDuy/dpdk-dev-patch-v2-i40e-fix-eth-i40e-dev-init-sequence-on-thunderx This patchset introduces 8-bit, 16-bit, 32bit, 64bit I/O device memory read/write operations along with the relaxed versions. The weakly-ord

[dpdk-dev] [PATCH 01/28] eal: introduce I/O device memory barriers

This commit introduce rte_io_mb(), rte_io_wmb() and rte_io_rmb(), in order to enable memory barriers between I/O device and CPU. Signed-off-by: Jerin Jacob --- lib/librte_eal/common/include/generic/rte_atomic.h | 27 ++ 1 file changed, 27 insertions(+) diff --git a/lib/librt

Re: [dpdk-dev] [PATCH] doc: fix environment variable typo

On 13/12/2016 21:40, Baruch Siach wrote: Signed-off-by: Baruch Siach --- doc/guides/sample_app_ug/ethtool.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Missing fixline Fixes: bda68ab9d1e7 ("examples/ethtool: add user-space ethtool sample application") Otherwise, well spotted.

Re: [dpdk-dev] [PATCH 20/31] app/testpmd: use VFD APIs on i40e

Hi Ferruh, > -Original Message- > From: Yigit, Ferruh > Sent: Wednesday, December 14, 2016 12:57 AM > To: Lu, Wenzhuo; dev@dpdk.org > Cc: Chen, Jing D; Iremonger, Bernard > Subject: Re: [dpdk-dev] [PATCH 20/31] app/testpmd: use VFD APIs on i40e > > On 12/2/2016 12:12 AM, Wenzhuo Lu wrote

Re: [dpdk-dev] [PATCH v2 25/32] app/testpmd: handle i40e in VF VLAN filter command

Hi Ferruh, > -Original Message- > From: Yigit, Ferruh > Sent: Tuesday, December 13, 2016 9:41 PM > To: Lu, Wenzhuo; dev@dpdk.org > Cc: Iremonger, Bernard > Subject: Re: [dpdk-dev] [PATCH v2 25/32] app/testpmd: handle i40e in VF VLAN > filter command > > Hi Wenzhuo, > > On 12/7/2016 3:32

Re: [dpdk-dev] [PATCH v2 01/12] eal: define container_of macro

On Tue, Dec 13, 2016 at 2:37 PM, Shreyansh Jain wrote: > From: Jan Blunck > > This macro is based on Jan Viktorin's original patch but also checks the > type of the passed pointer against the type of the member. > > Signed-off-by: Jan Viktorin > [shreyansh.j...@nxp.com: Fix checkpatch error] > S

Re: [dpdk-dev] [PATCH 04/13] acl: allow zero verdict

> -Original Message- > From: Michal Miroslaw [mailto:mirq-li...@rere.qmqm.pl] > Sent: Tuesday, December 13, 2016 6:03 PM > To: Ananyev, Konstantin > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH 04/13] acl: allow zero verdict > > On Tue, Dec 13, 2016 at 05:27:31PM +, Ananyev, Ko

Re: [dpdk-dev] [PATCH 02/13] mbuf: rte_pktmbuf_free_bulk()

On Tue, 13 Dec 2016 02:08:15 +0100 (CET) Michał Mirosław wrote: > Signed-off-by: Michał Mirosław > > --- > lib/librte_mbuf/rte_mbuf.h | 15 +++ > 1 file changed, 15 insertions(+) > > diff --git a/lib/librte_mbuf/rte_mbuf.h b/lib/librte_mbuf/rte_mbuf.h > index ead7c6e..a95d99f 1006

Re: [dpdk-dev] [PATCH v13 6/7] vmxnet3: add Tx preparation

Looks good and two nits below. > -Original Message- > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Tomasz Kulasek > Sent: Tuesday, December 13, 2016 9:42 AM > To: dev@dpdk.org > Cc: Ananyev, Konstantin > Subject: [dpdk-dev] [PATCH v13 6/7] vmxnet3: add Tx preparation > > From: "A

Re: [dpdk-dev] [PATCH 04/13] acl: allow zero verdict

On Tue, Dec 13, 2016 at 05:27:31PM +, Ananyev, Konstantin wrote: > > > > -Original Message- > > From: Michal Miroslaw [mailto:mirq-li...@rere.qmqm.pl] > > Sent: Tuesday, December 13, 2016 4:14 PM > > To: Ananyev, Konstantin > > Cc: dev@dpdk.org > > Subject: Re: [dpdk-dev] [PATCH 04/1

[dpdk-dev] [PATCH v13 7/7] testpmd: use Tx preparation in csum engine

Added "csum txprep (on|off)" command which allows to switch to the tx path using Tx preparation API. By default unchanged implementation is used. Using Tx preparation path, pseudo header calculation for udp/tcp/tso packets from application, and used Tx preparation API for packet preparation and v

[dpdk-dev] [PATCH v13 6/7] vmxnet3: add Tx preparation

From: "Ananyev, Konstantin" Signed-off-by: Konstantin Ananyev --- drivers/net/vmxnet3/vmxnet3_ethdev.c |4 +++ drivers/net/vmxnet3/vmxnet3_ethdev.h |2 ++ drivers/net/vmxnet3/vmxnet3_rxtx.c | 57 ++ 3 files changed, 63 insertions(+) diff --git a/driv

[dpdk-dev] [PATCH v13 5/7] ixgbe: add Tx preparation

Signed-off-by: Tomasz Kulasek Acked-by: Konstantin Ananyev --- drivers/net/ixgbe/ixgbe_ethdev.c |3 ++ drivers/net/ixgbe/ixgbe_ethdev.h |5 +++- drivers/net/ixgbe/ixgbe_rxtx.c | 56 ++ drivers/net/ixgbe/ixgbe_rxtx.h |2 ++ 4 files changed, 65

[dpdk-dev] [PATCH v13 4/7] i40e: add Tx preparation

Signed-off-by: Tomasz Kulasek Acked-by: Konstantin Ananyev --- drivers/net/i40e/i40e_ethdev.c |3 ++ drivers/net/i40e/i40e_rxtx.c | 74 +++- drivers/net/i40e/i40e_rxtx.h |8 + 3 files changed, 84 insertions(+), 1 deletion(-) diff --git a/dri

[dpdk-dev] [PATCH v13 3/7] fm10k: add Tx preparation

Signed-off-by: Tomasz Kulasek Acked-by: Konstantin Ananyev --- drivers/net/fm10k/fm10k.h|6 + drivers/net/fm10k/fm10k_ethdev.c |5 drivers/net/fm10k/fm10k_rxtx.c | 50 +- 3 files changed, 60 insertions(+), 1 deletion(-) diff --git

[dpdk-dev] [PATCH v13 2/7] e1000: add Tx preparation

Signed-off-by: Tomasz Kulasek Acked-by: Konstantin Ananyev --- drivers/net/e1000/e1000_ethdev.h | 11 drivers/net/e1000/em_ethdev.c|5 +++- drivers/net/e1000/em_rxtx.c | 48 ++- drivers/net/e1000/igb_ethdev.c |4 +++ drivers/net/e10

[dpdk-dev] [PATCH v13 1/7] ethdev: add Tx preparation

Added API for `rte_eth_tx_prepare` uint16_t rte_eth_tx_prepare(uint8_t port_id, uint16_t queue_id, struct rte_mbuf **tx_pkts, uint16_t nb_pkts) Added fields to the `struct rte_eth_desc_lim`: uint16_t nb_seg_max; /**< Max number of segments per whole packet. */

[dpdk-dev] [PATCH v13 0/7] add Tx preparation

As discussed in that thread: http://dpdk.org/ml/archives/dev/2015-September/023603.html Different NIC models depending on HW offload requested might impose different requirements on packets to be TX-ed in terms of: - Max number of fragments per packet allowed - Max number of fragments per TSO

Re: [dpdk-dev] [PATCH 06/13] null: fake PMD capabilities

On 12/13/2016 5:12 PM, Ananyev, Konstantin wrote: > > >> -Original Message- >> From: Michal Miroslaw [mailto:mirq-li...@rere.qmqm.pl] >> Sent: Tuesday, December 13, 2016 2:58 PM >> To: Ananyev, Konstantin >> Cc: dev@dpdk.org >> Subject: Re: [dpdk-dev] [PATCH 06/13] null: fake PMD capabil

Re: [dpdk-dev] [PATCH 04/13] acl: allow zero verdict

> -Original Message- > From: Michal Miroslaw [mailto:mirq-li...@rere.qmqm.pl] > Sent: Tuesday, December 13, 2016 4:14 PM > To: Ananyev, Konstantin > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH 04/13] acl: allow zero verdict > > On Tue, Dec 13, 2016 at 03:13:42PM +, Ananyev, Ko

Re: [dpdk-dev] [PATCH 06/13] null: fake PMD capabilities

> -Original Message- > From: Michal Miroslaw [mailto:mirq-li...@rere.qmqm.pl] > Sent: Tuesday, December 13, 2016 2:58 PM > To: Ananyev, Konstantin > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH 06/13] null: fake PMD capabilities > > On Tue, Dec 13, 2016 at 02:37:34PM +, Ananyev

Re: [dpdk-dev] [PATCH 20/31] app/testpmd: use VFD APIs on i40e

On 12/2/2016 12:12 AM, Wenzhuo Lu wrote: > The new VF Daemon (VFD) APIs is implemented on i40e. Change > testpmd code to use them, inlcuding VF MAC anti-spoofing, > VF VLAN anti-spoofing, TX loopback, VF VLAN strip, VF VLAN > insert. > > Signed-off-by: Wenzhuo Lu > Signed-off-by: Chen Jing D(Mark

[dpdk-dev] [PATCH v2] SDK: Add scripts to initialize DPDK runtime

From: Christian Ehrhardt A tools/init directory is added with dpdk-init, a script that can be used to initialize a DPDK runtime environment. 2 config files with default options, dpdk.conf and interfaces, are provided as well together with a SysV init script and a systemd service unit. v2: relice

Re: [dpdk-dev] [PATCH 04/13] acl: allow zero verdict

On Tue, Dec 13, 2016 at 05:14:09PM +0100, Michal Miroslaw wrote: > On Tue, Dec 13, 2016 at 03:13:42PM +, Ananyev, Konstantin wrote: [...] > > > Dear Konstantin, > > > > > > Can you describe how the ACL code treats zero specially? I could not find > > > anything, really. The only thing I found

Re: [dpdk-dev] [PATCH v2 08/13] PMD/af_packet: guard against buffer overruns in RX path

On Tue, Dec 13, 2016 at 02:28:34AM +0100, Michał Mirosław wrote: > > Signed-off-by: Michał Mirosław Acked-by: John W. Linville > --- > drivers/net/af_packet/rte_eth_af_packet.c | 11 ++- > 1 file changed, 6 insertions(+), 5 deletions(-) > > diff --git a/drivers/net/af_packet/rte_eth_

Re: [dpdk-dev] [PATCH v2 09/13] PMD/af_packet: guard against buffer overruns in TX path

On Tue, Dec 13, 2016 at 02:28:34AM +0100, Michał Mirosław wrote: > Signed-off-by: Michał Mirosław Acked-by: John W. Linville > --- > drivers/net/af_packet/rte_eth_af_packet.c | 20 +++- > 1 file changed, 15 insertions(+), 5 deletions(-) > > diff --git a/drivers/net/af_packet/r

Re: [dpdk-dev] [PATCH 04/13] acl: allow zero verdict

On Tue, Dec 13, 2016 at 03:13:42PM +, Ananyev, Konstantin wrote: [...] > > > > > > Subject: [dpdk-dev] [PATCH 04/13] acl: allow zero verdict > > > > > > > > > > > > Signed-off-by: Michał Mirosław > > > > > > --- > > > > > > lib/librte_acl/rte_acl.c | 3 +-- > > > > > > lib/librte_acl/

Re: [dpdk-dev] [PATCH] SDK: Add scripts to initialize DPDK runtime

Stefans mail got rejected by moderator (??!), reposting FYI as I'm subscribed and should autopass the moderation. On Tue, Dec 13, 2016 at 3:45 PM, Stefan Bader wrote: > On 13.12.2016 08:00, Christian Ehrhardt wrote: > > > > On Mon, Dec 12, 2016 at 10:58 PM, Luca Boccassi >

Re: [dpdk-dev] [PATCH 04/13] acl: allow zero verdict

> -Original Message- > From: Michal Miroslaw [mailto:mirq-li...@rere.qmqm.pl] > Sent: Tuesday, December 13, 2016 2:53 PM > To: Ananyev, Konstantin > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH 04/13] acl: allow zero verdict > > On Tue, Dec 13, 2016 at 02:14:19PM +, Ananyev, Ko

Re: [dpdk-dev] [PATCH v2 12/12] drivers: update PMDs to use rte_driver probe and remove

On 12/13/2016 1:52 PM, Andrew Rybchenko wrote: > On 12/13/2016 04:37 PM, Shreyansh Jain wrote: >> These callbacks now act as first layer of PCI interfaces from the Bus. >> Bus probe would enter the PMDs through the rte_driver->probe/remove >> callbacks, falling to rte_xxx_driver->probe/remove (Curr

Re: [dpdk-dev] [PATCH 06/13] null: fake PMD capabilities

On Tue, Dec 13, 2016 at 02:37:34PM +, Ananyev, Konstantin wrote: > > > > -Original Message- > > From: Michal Miroslaw [mailto:mirq-li...@rere.qmqm.pl] > > Sent: Tuesday, December 13, 2016 2:27 PM > > To: Ananyev, Konstantin > > Cc: dev@dpdk.org > > Subject: Re: [dpdk-dev] [PATCH 06/1

Re: [dpdk-dev] [PATCH 04/13] acl: allow zero verdict

On Tue, Dec 13, 2016 at 02:14:19PM +, Ananyev, Konstantin wrote: > > -Original Message- > > From: Michal Miroslaw [mailto:mirq-li...@rere.qmqm.pl] > > Sent: Tuesday, December 13, 2016 1:55 PM > > To: Ananyev, Konstantin > > Cc: dev@dpdk.org > > Subject: Re: [dpdk-dev] [PATCH 04/13] acl

Re: [dpdk-dev] [PATCH 06/13] null: fake PMD capabilities

> -Original Message- > From: Michal Miroslaw [mailto:mirq-li...@rere.qmqm.pl] > Sent: Tuesday, December 13, 2016 2:27 PM > To: Ananyev, Konstantin > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH 06/13] null: fake PMD capabilities > > On Tue, Dec 13, 2016 at 10:48:32AM +, Ananyev

Re: [dpdk-dev] [PATCH v2 17/32] net/i40e: set VF broadcast mode from PF

Hi Ferruh, > -Original Message- > From: Yigit, Ferruh > Sent: Wednesday, December 7, 2016 2:33 PM > To: Lu, Wenzhuo ; dev@dpdk.org > Cc: Iremonger, Bernard > Subject: Re: [dpdk-dev] [PATCH v2 17/32] net/i40e: set VF broadcast mode > from PF > > On 12/7/2016 3:32 AM, Wenzhuo Lu wrote: >

Re: [dpdk-dev] [PATCH 06/13] null: fake PMD capabilities

On Tue, Dec 13, 2016 at 10:48:32AM +, Ananyev, Konstantin wrote: > > -Original Message- > > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Michal Miroslaw > > Sent: Tuesday, December 13, 2016 1:08 AM > > To: dev@dpdk.org > > Subject: [dpdk-dev] [PATCH 06/13] null: fake PMD capabil

Re: [dpdk-dev] [PATCH 04/13] acl: allow zero verdict

> -Original Message- > From: Michal Miroslaw [mailto:mirq-li...@rere.qmqm.pl] > Sent: Tuesday, December 13, 2016 1:55 PM > To: Ananyev, Konstantin > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH 04/13] acl: allow zero verdict > > On Tue, Dec 13, 2016 at 10:36:16AM +, Ananyev, Ko

Re: [dpdk-dev] [PATCH 04/13] acl: allow zero verdict

On Tue, Dec 13, 2016 at 10:36:16AM +, Ananyev, Konstantin wrote: > Hi Michal, > > > -Original Message- > > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Michal Miroslaw > > Sent: Tuesday, December 13, 2016 1:08 AM > > To: dev@dpdk.org > > Subject: [dpdk-dev] [PATCH 04/13] acl: a

Re: [dpdk-dev] [PATCH v12] net/tap: new TUN/TAP device PMD

On 12/12/2016 2:38 PM, Keith Wiles wrote: > The PMD allows for DPDK and the host to communicate using a raw > device interface on the host and in the DPDK application. The device > created is a Tap device with a L2 packet header. > > v12- Fixup minor changes for driver_name and version number > v1

Re: [dpdk-dev] [PATCH v2 12/12] drivers: update PMDs to use rte_driver probe and remove

On 12/13/2016 04:37 PM, Shreyansh Jain wrote: These callbacks now act as first layer of PCI interfaces from the Bus. Bus probe would enter the PMDs through the rte_driver->probe/remove callbacks, falling to rte_xxx_driver->probe/remove (Currently, all the drivers are rte_pci_driver). I think si

[dpdk-dev] fm10k pmd limitations

Hey guys, I'm using dpdk 16.4 and fm10k card. According to the code, there's no support for disabling vlan stripping and VLAN QinQ in pmd fm10k. Does anybody know why? If there's any way to work-around it, or when is a behavior change expected? I need my VF to receive the packets with the VLAN

Re: [dpdk-dev] [PATCH v4 0/7] net/ixgbe: move set VF functions.

Hi Ferruh, > -Original Message- > From: Yigit, Ferruh > Sent: Tuesday, December 13, 2016 1:37 PM > To: Iremonger, Bernard ; > thomas.monja...@6wind.com; dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH v4 0/7] net/ixgbe: move set VF functions. > > On 12/13/2016 11:40 AM, Bernard Iremonger w

Re: [dpdk-dev] [PATCH v2 25/32] app/testpmd: handle i40e in VF VLAN filter command

Hi Wenzhuo, On 12/7/2016 3:32 AM, Wenzhuo Lu wrote: > modify set_vf_rx_vlan function to handle the i40e PMD. > > Signed-off-by: Bernard Iremonger > --- Latest applied patches [1] conflict with some testpmd patches of this patchset. Can you please rebase this patchset on top of the latest next-

[dpdk-dev] [PATCH] doc: fix environment variable typo

Signed-off-by: Baruch Siach --- doc/guides/sample_app_ug/ethtool.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/guides/sample_app_ug/ethtool.rst b/doc/guides/sample_app_ug/ethtool.rst index 4d1697e8a050..67797954d740 100644 --- a/doc/guides/sample_app_ug/ethtool.rst

Re: [dpdk-dev] [PATCH v4 0/7] net/ixgbe: move set VF functions.

On 12/13/2016 11:40 AM, Bernard Iremonger wrote: > This patchset implements the following deprecation notice: > [PATCH v1] doc: announce API and ABI change for librte_ether > > Changes in V4: > Fixed compile issues when ixgbe PMD is not present. > Removed duplicate testpmd commands. > Added clean

[dpdk-dev] [PATCH v2 11/12] eal: enable PCI bus

Register a PCI bus with Scan/match and probe callbacks. Necessary changes in EAL layer for enabling bus interfaces. PCI devices and drivers now reside within the Bus object. Now that PCI bus handles the scan/probe methods, independent calls to PCI scan and probe can be removed from the code. PCI d

[dpdk-dev] [PATCH v2 10/12] pci: Pass rte_pci_addr to functions instead of separate args

From: Ben Walker Instead of passing domain, bus, devid, func, just pass an rte_pci_addr. Signed-off-by: Ben Walker [Shreyansh: Checkpatch error fix] Signed-off-by: Shreyansh Jain --- lib/librte_eal/linuxapp/eal/eal_pci.c | 33 ++--- 1 file changed, 14 insertions(+)

[dpdk-dev] [PATCH v2 12/12] drivers: update PMDs to use rte_driver probe and remove

These callbacks now act as first layer of PCI interfaces from the Bus. Bus probe would enter the PMDs through the rte_driver->probe/remove callbacks, falling to rte_xxx_driver->probe/remove (Currently, all the drivers are rte_pci_driver). Signed-off-by: Shreyansh Jain --- drivers/net/bnx2x/bnx2x

[dpdk-dev] [PATCH v2 08/12] pci: split match and probe function

Matching of PCI device address and driver ID table is being done at two discreet locations duplicating the code. (rte_eal_pci_probe_one_driver and rte_eal_pci_detach_dev). Splitting the matching function into rte_eal_pci_match. Signed-off-by: Shreyansh Jain -- v2: - Change default return in ma

[dpdk-dev] [PATCH v2 09/12] eal/pci: generalize args of PCI scan/match towards RTE device/driver

PCI scan and match now work on rte_device/rte_driver rather than PCI specific objects. These functions can now be plugged to the generic bus callbacks for scanning and matching devices/drivers. Signed-off-by: Shreyansh Jain --- app/test/test_pci.c | 2 +- lib/librte_eal/bsda

[dpdk-dev] [PATCH v2 07/12] eal: enable probe from bus infrastructure

The model is: rte_eal_init `--> calls rte_eal_bus_probe() This iterates over all the drivers and devices and matches them. For matched bus specific device-driver and calls: `-> rte_driver->probe() for all matched device/drivers (rte_bus->match() successful) T

[dpdk-dev] [PATCH v2 06/12] eal: add probe and remove support for rte_driver

rte_driver now supports probe and remove. These would be used for generic device type (PCI, etc) probe and remove. Signed-off-by: Shreyansh Jain --- lib/librte_eal/common/include/rte_dev.h | 12 1 file changed, 12 insertions(+) diff --git a/lib/librte_eal/common/include/rte_dev.h

[dpdk-dev] [PATCH v2 05/12] eal: integrate bus scan and probe with EAL

Still a dummy implementation as no real bus driver exists. This adds calls from EAL to bus specific scan, match functions. Once driver->probe is in place, and a bus handler has been installed, the code would become effective. Signed-off-by: Shreyansh Jain --- lib/librte_eal/bsdapp/eal/eal.c

[dpdk-dev] [PATCH v2 04/12] eal/bus: add scan, match and insert support

When a PMD is registred, it will associate itself with a bus. A bus is responsible for 'scan' of all the devices attached to it. All the scanned devices are attached to bus specific device_list. During the probe operation, 'match' of the drivers and devices would be done. Also, rather than adding

[dpdk-dev] [PATCH v2 03/12] test: add basic bus infrastructure tests

Verification of bus registration, driver registration on a bus. Signed-off-by: Shreyansh Jain --- app/test/Makefile | 2 +- app/test/test.h | 2 + app/test/test_bus.c | 423 3 files changed, 426 insertions(+), 1 deletion(-) create m

[dpdk-dev] [PATCH v2 02/12] eal/bus: introduce bus abstraction

This patch introduces the rte_bus abstraction for devices and drivers in EAL framework. The model is: - One or more buses are connected to a CPU (or core) - One or more devices are conneted to a Bus - Drivers are running instances which manage one or more devices - Bus is responsible for identi

  1   2   >