Re: [dpdk-dev] Compilation failure when disabling Cavium OCTEONTX network PMD driver

2019-07-08 Thread Daniel Pharos
Huh, looks like I've been hitting "Reply" instead of the required "Reply all", and the mailing list got dropped from the CC. Below is our conversation so far (might be incomplete). Kind regards, DanielPharos From: Daniel Pharos Sent: 08 July 2019 22:50 To: Jerin Jac

[dpdk-dev] Compilation failure when disabling Cavium OCTEONTX network PMD driver

2019-07-07 Thread Daniel Pharos
Hi, If I disable the Cavium OCTEONTX network PMD driver in the config file (so: "CONFIG_RTE_LIBRTE_OCTEONTX_PMD=n"), compilation of DPDK 19.05 fails with: /home/ubuntu/Downloads/dpdk-19.05/build/lib/librte_pmd_octeontx_ssovf.a(ssovf_worker.o): In function `ssows_flush_events': ssovf_worker.c:(.t

Re: [dpdk-dev] MLX5: Array written to out-of-bounds when freeing memory

2019-01-20 Thread Daniel Pharos
Hi Yongseok, Thanks for the quick response! If there is any information you need that I may be able to provide, please just ask. Kind regards, DanielPharos -Original Message- From: Yongseok Koh Sent: 19 January 2019 08:15 To: Daniel Pharos Cc: dev@dpdk.org; Dekel Peled ; Olga Shern

[dpdk-dev] MLX5: Array written to out-of-bounds when freeing memory

2019-01-18 Thread Daniel Pharos
Hi, Recently I had the privilege of some play-time on a IBM Power 9 machine with a Mellanox MLX5-card in it. However, I encountered a seg fault problem using DPDK and DPDK-pktgen. It's the exact same one as somebody else encountered (also on a Power 9) here: https://bugzilla.redhat.com/show_bug

[dpdk-dev] Wrong constant being used

2019-01-09 Thread Daniel Pharos
Hi, In pktgen 3.6.1, app/pktgen.c, line 219, the constant "IPPROTO_UDP" is used. Shouldn't that be "PG_IPPROTO_UDP" instead? Kind regards, DanielPharos

[dpdk-dev] Seg fault with GRE in pktgen

2019-01-09 Thread Daniel Pharos
Hi, Using pktgen 3.6.1, I'm getting a seg fault when enabling GRE. In app/pktgen.c, on line 556 l3_hdr is set to NULL, and then on line 567 it is send to a function that calls memset on it, triggering the seg fault I'm seeing. I suppose that l3_hdr argument (and the last argument on line 569 to