avoid AltiVec keyword vectorThe AltiVec header file is defining "vector", except in C++ build.The keyword "vector" may conflict easily.As a rule, it is better to use the alternative keyword "__ve
avoid AltiVec keyword vectorThe AltiVec header file is defining "vector", except in C++ build.The keyword "vector" may conflict easily.As a rule, it is better to use the alternative keyword "__vector",so we will be able to #undef vector after including AltiVec header.Later it may become possible to #undef vector in rte_altivec.hwith a compatibility breakage.Signed-off-by: Thomas Monjalon <[email protected]>Reviewed-by: David Christensen <[email protected]>
show more ...
lib: remove unneeded header includesThese header includes have been flagged by the iwyu_tooland removed.Signed-off-by: Sean Morrissey <[email protected]>
lpm6: fix buffer overflowThis patch fixes buffer overflow reported by ASAN,please reference https://bugs.dpdk.org/show_bug.cgi?id=819The rte_lpm6 keeps routing information for control plane purp
lpm6: fix buffer overflowThis patch fixes buffer overflow reported by ASAN,please reference https://bugs.dpdk.org/show_bug.cgi?id=819The rte_lpm6 keeps routing information for control plane purposeinside the rte_hash table which uses rte_jhash() as a hash function.From the rte_jhash() documentation: If input key is not aligned tofour byte boundaries or a multiple of four bytes in length,the memory region just after may be read (but not used in thecomputation).rte_lpm6 uses 17 bytes keys consisting of IPv6 address (16 bytes) +depth (1 byte).This patch increases the size of the depth field up to uint32_tand sets the alignment to 4 bytes.Bugzilla ID: 819Fixes: 86b3b21952a8 ("lpm6: store rules in hash table")Cc: [email protected]Signed-off-by: Vladimir Medvedkin <[email protected]>Acked-by: Bruce Richardson <[email protected]>
build/windows: remove separate list of libsRather than maintaining a separate list of libraries which are to bebuilt on windows, use the standard library list and explicitly add toeach library th
build/windows: remove separate list of libsRather than maintaining a separate list of libraries which are to bebuilt on windows, use the standard library list and explicitly add toeach library that is not to be built a check for windows and disablethe library at that per-lib level. As well as shortening the mainlib/meson.build file, this also leads to the build summary at the end ofthe meson config run correctly listing the libraries which are not to bebuilt.Signed-off-by: Bruce Richardson <[email protected]>
version: 21.11-rc0Start a new release cycle with empty release notes.The ABI version becomes 22.0.The map files are updated to the new ABI major number (22).The ABI exceptions are dropped and C
version: 21.11-rc0Start a new release cycle with empty release notes.The ABI version becomes 22.0.The map files are updated to the new ABI major number (22).The ABI exceptions are dropped and CI ABI checks are disabled becausecompatibility is not preserved.Signed-off-by: Thomas Monjalon <[email protected]>Acked-by: Ferruh Yigit <[email protected]>Acked-by: David Marchand <[email protected]>
config/arm: fix SVE build with GCC 8.3If the target machine has SVE feature (e.g. "-march=armv8.2-a+sve'),and the compiler is gcc-8.3, it will produce this error: In file included from lib/eal/co
config/arm: fix SVE build with GCC 8.3If the target machine has SVE feature (e.g. "-march=armv8.2-a+sve'),and the compiler is gcc-8.3, it will produce this error: In file included from lib/eal/common/eal_common_options.c:38: lib/eal/arm/include/rte_vect.h:13:10: fatal error: arm_sve.h: No such file or directory #include <arm_sve.h> ^~~~~~~~~~~The root cause is that gcc-8.3 supports SVE (the macro__ARM_FEATURE_SVE was 1), but it doesn't support SVE ACLE [1].The solution:a) Detect compiler whether support SVE ACLE, if support then defineRTE_HAS_SVE_ACLE macro.b) Use the RTE_HAS_SVE_ACLE macro to include SVE header file.[1] ACLE: Arm C Language Extensions, the SVE ACLE header file is<arm_sve.h>, user should include it when writing ACLE SVE code.Fixes: 67b68824a82d ("lpm/arm: support SVE")Cc: [email protected]Signed-off-by: Chengwen Feng <[email protected]>Acked-by: Ruifeng Wang <[email protected]>Signed-off-by: Thomas Monjalon <[email protected]>
lib: remove librte_ prefix from directory namesThere is no reason for the DPDK libraries to all have 'librte_' prefix onthe directory names. This prefix makes the directory names longer and alsom
lib: remove librte_ prefix from directory namesThere is no reason for the DPDK libraries to all have 'librte_' prefix onthe directory names. This prefix makes the directory names longer and alsomakes it awkward to add features referring to individual libraries in thebuild - should the lib names be specified with or without the prefix.Therefore, we can just remove the library prefix and use the library'sunique name as the directory name, i.e. 'eal' rather than 'librte_eal'Signed-off-by: Bruce Richardson <[email protected]>