[DPDK/other Bug 1608] dpdk-dumpcap not allowed to do multiple invocations on the same interface

https://bugs.dpdk.org/show_bug.cgi?id=1608 Bug ID: 1608 Summary: dpdk-dumpcap not allowed to do multiple invocations on the same interface Product: DPDK Version: 23.11 Hardware: All OS: All Stat

[PATCH 3/3] drivers/net: add diagnostics macros to make code portable

It was a common pattern to have "GCC diagnostic ignored" pragmas sprinkled over the code and only activate these pragmas for certain compilers (gcc and clang). Clang supports GCC’s pragma for compatibility with existing source code, so #pragma GCC diagnostic and #pragma clang diagnostic are synonym

[PATCH 2/3] drivers/common: add diagnostics macros to make code portable

It was a common pattern to have "GCC diagnostic ignored" pragmas sprinkled over the code and only activate these pragmas for certain compilers (gcc and clang). Clang supports GCC’s pragma for compatibility with existing source code, so #pragma GCC diagnostic and #pragma clang diagnostic are synonym

[PATCH 0/3] add diagnostics macros to make code portable

It was a common pattern to have "GCC diagnostic ignored" pragmas sprinkled over the code and only activate these pragmas for certain compilers (gcc and clang). Clang supports GCCΓÇÖs pragma for compatibility with existing source code, so #pragma GCC diagnostic and #pragma clang diagnostic are synon

[PATCH 1/3] lib/eal: add diagnostics macros to make code portable

It was a common pattern to have "GCC diagnostic ignored" pragmas sprinkled over the code and only activate these pragmas for certain compilers (gcc and clang). Clang supports GCC’s pragma for compatibility with existing source code, so #pragma GCC diagnostic and #pragma clang diagnostic are synonym

[PATCH 2/2] drivers_net: fix void function returning a value

This patch avoids warnings like the one below emitted by MSVC: ../drivers/common/idpf/idpf_common_rxtx_avx512.c(139): warning C4098: 'idpf_singleq_rearm': 'void' function returning a value Signed-off-by: Andre Muezerie --- drivers/net/i40e/i40e_rxtx_vec_avx2.c | 2 +- drivers/net/i40e

[PATCH 1/2] drivers_common: fix void function returning a value

This patch avoids warnings like the one below emitted by MSVC: ../drivers/common/idpf/idpf_common_rxtx_avx512.c(139): warning C4098: 'idpf_singleq_rearm': 'void' function returning a value Signed-off-by: Andre Muezerie --- drivers/common/idpf/idpf_common_rxtx_avx512.c | 12

[PATCH 0/2] fix void function returning a value

This patch avoids warnings like the one below emitted by MSVC: ../drivers/common/idpf/idpf_common_rxtx_avx512.c(139): warning C4098: 'idpf_singleq_rearm': 'void' function returning a value Andre Muezerie (2): drivers_common: fix void function returning a value drivers_net: fix void fu

[PATCH] drivers_net: use 64-bit shift and avoid signed/unsigned mismatch

This patch avoids warnings like the ones below emitted by MSVC: 1) ../drivers/net/ice/base/ice_flg_rd.c(71): warning C4334: '<<': result of 32-bit shift implicitly converted to 64 bits (was 64-bit shift intended?) 2) ../drivers/net/ice/ice_dcf_sched.c(177): warning C4018: '>=': signed

[PATCH 2/2] drivers/net: remove use of non-standard array range initialization

Array range initialization is non-standard and is not provided by all compilers. MSVC does not implement it and ends up emitting errors like the one below: drivers/net/r8169/r8169_phy.c(380): error C2143: syntax error: missing ':' before '...' case CFG_METHOD_48 ... CFG_METHOD_57: The fix is

[PATCH 1/2] app/test: remove use of non-standard array range initialization

Array range initialization is non-standard and is not provided by all compilers. MSVC does not implement it and ends up emitting errors like the one below: drivers/net/r8169/r8169_phy.c(380): error C2143: syntax error: missing ':' before '...' case CFG_METHOD_48 ... CFG_METHOD_57: The fix is

[PATCH 0/2] remove use of non-standard array range initialization

Array range initialization is non-standard and is not provided by all compilers. MSVC does not implement it and ends up emitting errors like the one below: drivers/net/r8169/r8169_phy.c(380): error C2143: syntax error: missing ':' before '...' case CFG_METHOD_48 ... CFG_METHOD_57: The fix is

[DPDK/eventdev Bug 1607] cnkx eventdev drivers take too long to compile

https://bugs.dpdk.org/show_bug.cgi?id=1607 Bug ID: 1607 Summary: cnkx eventdev drivers take too long to compile Product: DPDK Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: minor

[PATCH 1/2] drivers/common: remove unused variables and add MSVC compiler flag

Removed unused variables and added MSVC specific compiler flag to ignore warnings about unused variables, like is being done for other compilers. Signed-off-by: Andre Muezerie --- drivers/common/idpf/base/meson.build | 13 ++--- drivers/common/idpf/idpf_common_rxtx.c | 2 -- d

[PATCH 2/2] drivers/net: remove unused variables and add MSVC compiler flag

Removed unused variables and added MSVC specific compiler flag to ignore warnings about unused variables, like is being done for other compilers. Signed-off-by: Andre Muezerie --- drivers/net/ice/base/ice_switch.c | 2 -- drivers/net/ice/base/meson.build | 16 ++--- drivers/net/qede/base

[PATCH 0/2] remove unused variables and add MSVC compiler flag

Removed unused variables and added MSVC specific compiler flag to ignore warnings about unused variables, like is being done for other compilers. Signed-off-by: Andre Muezerie Andre Muezerie (2): drivers/common: remove unused variables and add MSVC compiler flag drivers/net: remove unused va

[PATCH] Fix unused memseg length for memory issue

Fix the issue where OS memory is mistakenly freed with rte_free by setting the length (len) of unused memseg to 0. When eal_legacy_hugepage_init releases the VA space for unused memseg lists, it does not reset their length to 0. As a result, mlx5_mem_is_rte may incorrectly identify OS memory as DP