On Fri, 2019-04-05 at 21:09 +0200, Thomas Monjalon wrote:
> 05/04/2019 20:47, Jerin Jacob Kollanukkaran:
> > From: Thomas Monjalon
> > > 18/03/2019 17:50, Jerin Jacob Kollanukkaran:
> > > > From: Jerin Jacob
> > > >
> > > > Optimized configuration for Marvell thunderx2 SoC.
> > > > Updated meson
> -Original Message-
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Fan Zhang
> Sent: Friday, April 5, 2019 5:04 PM
> To: dev@dpdk.org
> Cc: akhil.go...@nxp.com; Zhang, Roy Fan ;
> sta...@dpdk.org
> Subject: [dpdk-dev] [PATCH v2] crypto/virtio: fix iv offset
>
> This patch fixe
From: Jerin Jacob
Use CRC32 instruction only when it is available to avoid
the build issue like below.
{standard input}:16: Error:
selected processor does not support `crc32cx w3,w3,x0'
Fixes: ea7be0a0386e ("lib/librte_table: add hash function headers")
Cc: Gavin Hu
Cc: sta...@dpdk.org
Signed
Hi,
We're seeing something similar to what is described in thread below. Our
product uses dpdk 17.08. Was there ever a resolution to Souvik's issue?
Thanks...Jim
On 01/04/2015 06:00, Dey, Souvik wrote:
> Hi All,
> We have a single primary application with multiple secondary
>
From: Jerin Jacob
Optimized configuration for Marvell octeontx2 SoC.
Updated meson build to support Marvell octeontx2 SoC.
Added meson cross build target for octeontx2.
Signed-off-by: Jerin Jacob
Signed-off-by: Pavan Nikhilesh
Reviewed-by: Gavin Hu
---
config/arm/arm64_octeontx2_linux_gcc
From: Jerin Jacob
Optimized configuration for Marvell thunderx2 SoC.
Updated meson build to support Marvell thunderx2 SoC.
Added meson cross compile target.
Product details are here:
https://www.marvell.com/server-processors/thunderx2-arm-processors/
Signed-off-by: Jerin Jacob
Signed-off-by:
From: Pavan Nikhilesh
Currently, RTE_* flags are set based on the implementer ID but there might
be some micro arch specific differences from the same vendor
eg. CACHE_LINESIZE. Add support to set micro arch specific flags.
Signed-off-by: Pavan Nikhilesh
Signed-off-by: Jerin Jacob
---
config/
From: Jerin Jacob
Introduce rte_cc_has_argument() Makefile helper to
check a given argument is support by the compiler.
Example Usage:
include $(RTE_SDK)/mk/rte.helper.mk
MACHINE_CFLAGS += $(call rte_cc_has_argument, -mcpu=octeontx2)
This would allow adding -mcpu=octeontx2 in MACHINE_CFLAGS
if
On 4/4/19 7:54 PM, Stephen Hemminger wrote:
On Sat, 30 Mar 2019 08:41:33 -0400
Chas Williams <3ch...@gmail.com> wrote:
Unfortunately, I think the complete fix is more complicated than this.
Drivers that use rte_vlan_insert don't anticipate that the mbuf might
change and that (hardware) trans
Hey Thomas,
Thanks for taking a look.
My intentions is to port some of the new features on top of this patch (flow
steering, ESP RSS – preparing the patches right now) which we are using inhouse
to DPDK, however for that I require to upgrade definitions.
The ownership of this definitions is VMwa
Allocated mempools were never free. it is bad practice.
Fixes: af75078fece3 ("first public release")
Cc: sta...@dpdk.org
Signed-off-by: Shahaf Shuler
---
app/test-pmd/testpmd.c | 24 ++--
1 file changed, 18 insertions(+), 6 deletions(-)
diff --git a/app/test-pmd/testpmd.c b
providing a command line parameter to set the mempool flags accordingly.
This mode is relevant only when creating an empty mempool and then
populating with memory.
Signed-off-by: Shahaf Shuler
Acked-by: Anatoly Burakov
---
app/test-pmd/parameters.c | 13 +
app/test-pmd/t
Small series to use the APIs introduced by commit c33a675b6276 ("bus: introduce
device level DMA memory mapping")
On v4:
* simplify return logic from mbuf_pool_create.
* remove extern from mempools structure.
On v3:
* remove redundant return.
On v2:
* enforcing parameter validity at option
Mempools can be populated with anonymous memory when using command line
parameter --mp-alloc=anon.
Considering the mempools are going to be used by the net devices,
it is better to DMA map this memory.
This patch add such mapping now that we have the APIs in place[1].
[1] commit c33a675b6276 ("b
14 matches
Mail list logo
