[dpdk-dev] Clarification for - SoC specific driver based common sub component placing

> -Original Message- > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > Sent: Friday, November 18, 2016 7:13 PM > To: Hemant Agrawal > Cc: dev at dpdk.org > Subject: Re: Clarification for - SoC specific driver based common sub > component > placi

[dpdk-dev] Clarification for - SoC specific driver based common sub component placing

Hi all, We like to introduce NXP's DPAA (Data Path Acceleration Architecture Gen2) Poll mode drivers into the DPDK. We need some clarification w.r.t the right placing of some dependent components, which can be common across drivers. E.g. We have hardware queue and buffer manager driver. This

[dpdk-dev] pmdinfogen issues: cross compilation for ARM fails with older host compiler

> -Original Message- > From: Neil Horman [mailto:nhorman at tuxdriver.com] > On Tue, Nov 15, 2016 at 09:34:16AM +0000, Hemant Agrawal wrote: > > > On Mon, Nov 14, 2016 at 02:29:24AM +0530, Jerin Jacob wrote: > > > > On Fri, Nov 11, 2016 at 10:34:39

[dpdk-dev] pmdinfogen issues: cross compilation for ARM fails with older host compiler

> On Mon, Nov 14, 2016 at 02:29:24AM +0530, Jerin Jacob wrote: > > On Fri, Nov 11, 2016 at 10:34:39AM +0000, Hemant Agrawal wrote: > > > Hi Neil, > > >Pmdinfogen compiles with host compiler. It usages > > > rte_byteorder.h > of the targ

[dpdk-dev] [PATCH v2] mempool: Free memzone if mempool populate phys fails

From: Nipun Gupta This patch fixes the issue of memzone not being freed incase the rte_mempool_populate_phys fails in the rte_mempool_populate_default This issue was identified when testing with OVS ~2.6 - configure the system with low memory (e.g. < 500 MB) - add bridge

[dpdk-dev] [PATCH] mempool: Free memzone if mempool populate phys fails

From: Nipun Gupta This fixes the issue of memzone not being freed, if the rte_mempool_populate_phys fails in the rte_mempool_populate_default This issue was identified when testing with OVS ~2.6 - configure the system with low memory (e.g. < 500 MB) - add bridge and dpdk

[dpdk-dev] pmdinfogen issues: cross compilation for ARM fails with older host compiler

..@broadcom.com] Sent: Wednesday, September 14, 2016 7:18 PM To: Hemant Agrawal Cc: Thomas Monjalon ; users at dpdk.org Subject: Re: [dpdk-users] Cross compile for ARM64 fails due to librte_vhost and pmdinfogen issues Hi Hemant, Thanks for the pointer to the 4.9.3 version. Haven't had issues with 4.

[dpdk-dev] [PATCH v3 2/2] mempool: pktmbuf pool default fallback for mempool ops error

Hi Olivier, > -Original Message- > From: Olivier Matz [mailto:olivier.matz at 6wind.com] > Sent: Friday, October 14, 2016 5:41 PM > > On 9/22/2016 6:42 PM, Hemant Agrawal wrote: > >> Hi Olivier > >> > >> On 9/19/2016 7:27 PM, Olivier Matz wrote:

[dpdk-dev] [PATCHv3] examples/l3fwd: em: use hw accelerated crc hash function for arm64

if machine level CRC extension are available, offload the hash to machine provide functions e.g. armv8-a CRC extensions support it Signed-off-by: Hemant Agrawal Reviewed-by: Jerin Jacob --- examples/l3fwd/l3fwd_em.c | 24 ++-- 1 file changed, 14 insertions(+), 10 deletions

[dpdk-dev] [PATCH v2] examples/l3fwd: em: use hw accelerated crc hash function for arm64

On 10/13/2016 7:06 PM, Jerin Jacob wrote: > On Fri, Oct 14, 2016 at 12:17:05AM +0530, Hemant Agrawal wrote: >> if machine level CRC extension are available, offload the >> hash to machine provide functions e.g. armv8-a CRC extensions >> support it >> >> Signed-of

[dpdk-dev] [RFC] [PATCH v2] libeventdev: event driven programming model framework for DPDK

Hi Bill/Jerin, > > Thanks for the review. > > [snip] > > > + * If the device init operation is successful, the correspondence > > > + between > > > + * the device identifier assigned to the new device and its > > > + associated > > > + * *rte_event_dev* structure is effectively registered. > >

[dpdk-dev] [PATCH v2] examples/l3fwd: em: use hw accelerated crc hash function for arm64

if machine level CRC extension are available, offload the hash to machine provide functions e.g. armv8-a CRC extensions support it Signed-off-by: Hemant Agrawal Reviewed-by: Jerin Jacob --- examples/l3fwd/l3fwd_em.c | 24 ++-- 1 file changed, 14 insertions(+), 10 deletions

[dpdk-dev] [PATCH v3 2/2] mempool: pktmbuf pool default fallback for mempool ops error

Hi Olivier, Any updates w.r.t this patch set? Regards Hemant On 9/22/2016 6:42 PM, Hemant Agrawal wrote: > Hi Olivier > > On 9/19/2016 7:27 PM, Olivier Matz wrote: >> Hi Hemant, >> >> On 09/16/2016 06:46 PM, Hemant Agrawal wrote: >>> In the rte_pktmbuf_

[dpdk-dev] [RFC] libeventdev: event driven programming model framework for DPDK

Hi Jerin/Narender, Thanks for the proposal and discussions. I agree with many of the comment made by Narender. Here are some additional comments. 1. rte_event_schedule - should support option for bulk dequeue. The size of bulk should be a property of device, how much depth

[dpdk-dev] [PATCH] examples/l3fwd: em path hash offload to machine

Hi Jerin, Thanks for the review, I will send a v2 with the suggestions made Regards, Hemant > -Original Message- > From: Jerin Jacob [mailto:jerin.jacob at caviumnetworks.com] > Sent: Wednesday, October 05, 2016 5:23 PM > To: Hemant Agrawal > Cc: dev at dpdk.or

[dpdk-dev] [RFC 0/7] changing mbuf pool handler

Hi Olivier, > -Original Message- > From: Hunt, David [mailto:david.hunt at intel.com] > Hi Olivier, > > > On 3/10/2016 4:49 PM, Olivier Matz wrote: > > Hi Hemant, > > > > Thank you for your feedback. > > > > On 09/22/2016 01:52 PM, Hemant

[dpdk-dev] [PATCH v3 00/15] Introduce SoC device/driver framework for EAL

> -Original Message- > From: Jan Viktorin [mailto:viktorin at rehivetech.com] > On Sun, 18 Sep 2016 16:56:54 +0800 > Jianbo Liu wrote: > > > On 18 September 2016 at 15:22, Jan Viktorin > wrote: > > > On Sun, 18 Sep 2016 13:58:50 +0800 > > > Jianbo Liu wrote: > > > > > >> On 9

[dpdk-dev] [PATCH v3 2/2] mempool: pktmbuf pool default fallback for mempool ops error

In the rte_pktmbuf_pool_create, if the default external mempool is not available, the implementation can default to "ring_mp_mc", which is an software implementation. Signed-off-by: Hemant Agrawal --- Changes in V3: * adding warning message to say that falling back to default sw poo

[dpdk-dev] [PATCH v3 1/2] eal/mempool: check for external mempool support

is not supporting the given mempool. Thereby allowing it to fallback on software mempool implementation e.g. "ring_mp_mc" This patch introduces new optional "supported" as mempool ops function to check if external mempool instance is available or not. Signed-off-by: Hemant Agrawal --- Ch

[dpdk-dev] [PATCH v2 2/2] mempool:pktmbuf pool default fallback for mempool ops error

Hi David, > -Original Message- > From: Hunt, David [mailto:david.hunt at intel.com] > Sent: Friday, September 16, 2016 2:00 PM > To: Hemant Agrawal ; olivier.matz at 6wind.com > Cc: dev at dpdk.org; jerin.jacob at caviumnetworks.com > Subject: Re: [PATCH v2 2/2] me

[dpdk-dev] [PATCH v2 1/2] eal/mempool: introduce check for external mempool availability

HI David, > -Original Message- > From: Hunt, David [mailto:david.hunt at intel.com] > Sent: Friday, September 16, 2016 2:44 PM > To: Hemant Agrawal ; olivier.matz at 6wind.com > Cc: dev at dpdk.org; jerin.jacob at caviumnetworks.com > Subject: Re: [PATCH v2 1/2] eal/

[dpdk-dev] [PATCH v2 2/2] mempool:pktmbuf pool default fallback for mempool ops error

In the rte_pktmbuf_pool_create, if the default external mempool is not available, the implementation can default to "ring_mp_mc", which is an software implementation. Signed-off-by: Hemant Agrawal --- lib/librte_mbuf/rte_mbuf.c | 5 + 1 file changed, 5 insertions(+) diff -

[dpdk-dev] [PATCH v2 1/2] eal/mempool: introduce check for external mempool availability

is not supporting the given mempool. Thereby allowing it to fallback on software mempool implementation e.g. "ring_mp_mc" This patch introduces new optional "pool_verify" as mempool ops function to check if external mempool instance is available or not. Signed-off-by: Hemant Agrawal --- Ch

[dpdk-dev] [PATCH 2/2] mempool:pktmbuf pool default fallback for mempool ops error

In the rte_pktmbuf_pool_create, if the default external mempool is not available, the implementation can default to "ring_mp_mc", which is an software implementation. Signed-off-by: Hemant Agrawal --- lib/librte_mbuf/rte_mbuf.c | 5 + 1 file changed, 5 insertions(+) diff -

[dpdk-dev] [PATCH 1/2] eal/mempool: introduce check for external mempool availability

is not supporting the given mempool. Thereby allowing it to fallback on software mempool implementation e.g. "ring_mp_mc" This patch introduces new optional "pool_verify" as mempool ops function to check if external mempool instance is available or not. Signed-off-by: Hemant Agrawal ---

[dpdk-dev] [PATCH] examples/l3fwd: enabling 4m hash for all 64 bit archs

This patch enables the support for 4 million hash entries for all 64 bit architectures. Signed-off-by: Hemant Agrawal --- examples/l3fwd/l3fwd.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/l3fwd/l3fwd.h b/examples/l3fwd/l3fwd.h index d8798b7..011ba14 100644

[dpdk-dev] [PATCH] examples/l3fwd: em path hash offload to machine

if machine level CRC extension are available, offload the hash to machine provided functions e.g. armv8-a CRC extensions support it Signed-off-by: Hemant Agrawal --- examples/l3fwd/l3fwd_em.c | 20 ++-- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/examples

[dpdk-dev] [PATCH] eal/armv8: high-resolution cycle counter

uring the > PMU from the privileged mode (kernel space). > > by default rte_rdtsc() implementation uses portable > cntvct_el0 scheme. Application can choose the PMU based implementation with > CONFIG_RTE_ARM_EAL_RDTSC_USE_PMU > > Signed-off-by: Jerin Jacob Acked-by: Hemant Agrawal

[dpdk-dev] usages issue with external mempool

Hi Oliver > -Original Message- > From: Olivier MATZ [mailto:olivier.matz at 6wind.com] > Sent: Thursday, July 28, 2016 2:03 PM > On 07/27/2016 11:51 AM, Jerin Jacob wrote: > > On Tue, Jul 26, 2016 at 10:11:13AM +0000, Hemant Agrawal wrote: > >> Hi, > >&g

[dpdk-dev] usages issue with external mempool

> -Original Message- > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > Sent: Wednesday, July 27, 2016 7:05 PM > To: Hemant Agrawal > Cc: Jerin Jacob ; David Hunt > ; dev at dpdk.org; olivier.matz at 6wind.com; > viktorin at rehivetech.com; Shreyans

[dpdk-dev] usages issue with external mempool

> -Original Message- > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > 2016-07-27 15:21, Jerin Jacob: > > On Tue, Jul 26, 2016 at 10:11:13AM +, Hemant Agrawal wrote: > > > This is not a user friendly approach to ask for changing 1 API to 6 new

[dpdk-dev] usages issue with external mempool

Hi, There was lengthy discussions w.r.t external mempool patches. However, I am still finding usages issue with the agreed approach. The existing API to create packet mempool, "rte_pktmbuf_pool_create" does not provide the option to change the object init iterator. This may be

[dpdk-dev] [PATCH 2/2] example/ipsec-secgw: add support for cryptodev_start

The usual device sequence is configure, queue setup and start. Crypto device should be started before use. Signed-off-by: Akhil Goyal Signed-off-by: Hemant Agrawal --- examples/ipsec-secgw/ipsec-secgw.c | 4 1 file changed, 4 insertions(+) diff --git a/examples/ipsec-secgw/ipsec-secgw.c

[dpdk-dev] [PATCH 1/2] example/l2fwd-crypto: add support for cryptodev_start

The usual device sequence is configure, queue setup and start. Crypto device should be started before use. Signed-off-by: Akhil Goyal Signed-off-by: Hemant Agrawal --- examples/l2fwd-crypto/main.c | 6 ++ 1 file changed, 6 insertions(+) diff --git a/examples/l2fwd-crypto/main.c b/examples

[dpdk-dev] [PATCHv3 1/2] config/armv8a: disable igb_uio

> -Original Message- > From: Jianbo Liu [mailto:jianbo.liu at linaro.org] > Sent: Friday, May 13, 2016 7:13 AM > To: Santosh Shukla > Cc: Stephen Hemminger ; Jerin Jacob > ; Hemant Agrawal > ; dev at dpdk.org; Thomas Monjalon > > Subject: Re: [dpdk-dev]

[dpdk-dev] [PATCHv3 2/2] mk: Introduce NXP dpaa2 architecture based on armv8-a

This patch introduces dpaa2 machine target to address difference in cpu parameter, number of core to 8 and no numa support w.r.t default armv8-a machine Signed-off-by: Hemant Agrawal --- config/defconfig_arm64-dpaa2-linuxapp-gcc | 42 ++ mk/machine/dpaa2/rte.vars.mk

[dpdk-dev] [PATCHv3 1/2] config/armv8a: disable igb_uio

IGB_UIO not supported for arm64 arch in kernel so disable. Signed-off-by: Hemant Agrawal Reviewed-by: Santosh Shukla --- config/defconfig_arm64-armv8a-linuxapp-gcc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/config/defconfig_arm64-armv8a-linuxapp-gcc b/config/defconfig_arm64-armv8a

[dpdk-dev] [PATCHv2 2/2] mk: Introduce NXP dpaa2 architecture based on armv8-a

This patch introduces dpaa2 machine target to address difference in cpu parameter, number of core to 8 and no numa support w.r.t default armv8-a machine Signed-off-by: Hemant Agrawal --- config/defconfig_arm64-dpaa2-linuxapp-gcc | 42 ++ mk/machine/dpaa2/rte.vars.mk

[dpdk-dev] [PATCHv2 1/2] mk:disabling CONFIG_RTE_EAL_IGB_UIO for armv8a

The compilation with upstream kernel is broken with this config as enabled. Signed-off-by: Hemant Agrawal --- config/defconfig_arm64-armv8a-linuxapp-gcc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/config/defconfig_arm64-armv8a-linuxapp-gcc b/config/defconfig_arm64-armv8a-linuxapp-gcc

[dpdk-dev] [PATCH] mk: Introduce NXP dpaa2 architecture based on armv8-a

This patch introduces dpaa2 machine target to address difference in cpu parameter, number of core to 8 and no numa support w.r.t default armv8-a machine Signed-off-by: Hemant Agrawal --- config/defconfig_arm64-dpaa2-linuxapp-gcc | 44 +++ mk/machine/dpaa2/rte.vars.mk

[dpdk-dev] [PATCH] mk: Introduce NXP dpaa2 architecture based on armv8-a

From: Santosh Shukla [mailto:sshu...@mvista.com] Sent: Monday, May 09, 2016 2:44 PM To: Jerin Jacob Cc: Hemant Agrawal ; dpdk ; Jianbo Liu ; Shukla, Santosh Subject: Re: [dpdk-dev] [PATCH] mk: Introduce NXP dpaa2 architecture based on armv8-a On Mon, May 9, 2016 at 2:36 PM, Jerin Jacob

[dpdk-dev] [PATCH] mk: Introduce NXP dpaa2 architecture based on armv8-a

-Original Message- From: Thomas Monjalon [mailto:thomas.monja...@6wind.com] Sent: Monday, May 09, 2016 2:10 PM To: Hemant Agrawal Cc: dev at dpdk.org Subject: Re: [dpdk-dev] [PATCH] mk: Introduce NXP dpaa2 architecture based on armv8-a 2016-05-09 19:18, Hemant Agrawal: > This pa

[dpdk-dev] [PATCH] kni:optimization of rte_kni_rx_burst

From: Hemant Agrawal <hem...@freescale.com> if any buffer is read from the tx_q, MAX_BURST buffers will be allocated and attempted to be added to to the alloc_q. This seems terribly inefficient and it also looks like the alloc_q will quickly fill to its maximum capacity. If the system b

[dpdk-dev] [PATCH] kni: optimizing the rte_kni_rx_burst

if alloc_q is full. The logic has been changed to: 1. Initially allocand add buffer(burstsize) to alloc_q 2. Add buffers to alloc_q only when you are pulling out the buffers. Signed-off-by: Hemant Agrawal --- lib/librte_kni/rte_kni.c |8 ++-- 1 file changed, 6 insertions(+), 2 deletions