Changes in dpdk

f2340c85 - config/arm: add platform config option

Wed, 14 Apr 2021 13:00:00 +0000

config/arm: add platform config optionAdd Arm SoC configuration sets to Arm meson.build and add an archagnostic meson option, 'platform', to select from these SoCconfigurations for meson native builds. This is preferable tospecifying a cross file when doing aarch64 -> aarch64 builds, since thecross file specifies the toolchain as well.Signed-off-by: Juraj Linkeš Reviewed-by: Honnappa Nagarahalli Reviewed-by: Ruifeng Wang Tested-by: Pavan Nikhilesh List of files: /dpdk/config/arm/arm64_armada_linux_gcc/dpdk/config/arm/arm64_armv8_linux_gcc/dpdk/config/arm/arm64_bluefield_linux_gcc/dpdk/config/arm/arm64_dpaa_linux_gcc/dpdk/config/arm/arm64_emag_linux_gcc/dpdk/config/arm/arm64_graviton2_linux_gcc/dpdk/config/arm/arm64_n1sdp_linux_gcc/dpdk/config/arm/arm64_n2_linux_gcc/dpdk/config/arm/arm64_stingray_linux_gcc/dpdk/config/arm/arm64_thunderx2_linux_gcc/dpdk/config/arm/arm64_thunderxt88_linux_gcc

33e71acf - drivers: remove octeontx2 drivers

Sat, 11 Dec 2021 09:00:00 +0000

drivers: remove octeontx2 driversAs per the deprecation notice, In the view of enabling unified driverfor octeontx2(cn9k)/octeontx3(cn10k), removing drivers/octeontx2drivers and replace with drivers/cnxk/ whichsupports both octeontx2(cn9k) and octeontx3(cn10k) SoCs.This patch does the following- Replace drivers/common/octeontx2/ with drivers/common/cnxk/- Replace drivers/mempool/octeontx2/ with drivers/mempool/cnxk/- Replace drivers/net/octeontx2/ with drivers/net/cnxk/- Replace drivers/event/octeontx2/ with drivers/event/cnxk/- Replace drivers/crypto/octeontx2/ with drivers/crypto/cnxk/- Rename config/arm/arm64_octeontx2_linux_gcc as config/arm/arm64_cn9k_linux_gcc- Update the documentation and MAINTAINERS to reflect the same.- Change the reference to OCTEONTX2 as OCTEON 9. Old release notes andthe kernel related documentation is not accounted for this change.Signed-off-by: Jerin Jacob Acked-by: Ferruh Yigit Acked-by: Akhil Goyal Acked-by: Ruifeng Wang List of files: /dpdk/config/arm/arm64_cn10k_linux_gcc/dpdk/config/arm/arm64_cn9k_linux_gcc

e754875c - config/arm: add aarch32 cross-compilation

Wed, 07 Jul 2021 13:00:00 +0000

config/arm: add aarch32 cross-compilationCreate meson cross file arm32_armv8a_linux_gcc. Use arm-linux-gnueabihf-toolset which comes with standard packages on most used systems, such asUbuntu and CentOS.Signed-off-by: Juraj Linkeš Acked-by: Ruifeng Wang List of files: /dpdk/config/arm/arm32_armv8_linux_gcc

9f077f1d - config/arm: add Qualcomm Centriq 2400

Fri, 07 May 2021 08:00:00 +0000

config/arm: add Qualcomm Centriq 2400From the documentation:"The SoC configuration is a combination of implementer and CPU part number configuration and SoC-specific configuration."Align Qualcomm SoC configuration with the configuration of otherserver SoCs (eMAG, Kunpeng 9x0): add a soc configuration to the existingimplementer configuration, and a cross file.Signed-off-by: Thierry Herbelot Acked-by: Ruifeng Wang List of files: /dpdk/config/arm/arm64_centriq2400_linux_gcc

3f6f8362 - support python 3 only

Wed, 30 Sep 2020 11:00:00 +0000

support python 3 onlyChanged scripts to explicitly use Python 3 only, to avoidmaintaining Python 2.Removed deprecation notices.Signed-off-by: Louise Kilheeney Signed-off-by: Kevin Laatz Acked-by: Bruce Richardson Acked-by: Robin Jarry Acked-by: Stephen Hemminger Acked-by: Ray Kinsella List of files: /dpdk/config/arm/armv8_machine.py

7cf32a22 - config/arm: add Hisilicon kunpeng

Fri, 16 Apr 2021 09:00:00 +0000

config/arm: add Hisilicon kunpengHere adds configs for Kunpeng server.Signed-off-by: Chengchang Tang Signed-off-by: Lijun Ou Acked-by: Jerin Jacob Reviewed-by: Ruifeng Wang List of files: /dpdk/config/arm/arm64_kunpeng920_linux_gcc/dpdk/config/arm/arm64_kunpeng930_linux_gcc

-

Tue, 22 Aug 2023 05:00:00 +0000

List of files: /dpdk/config/arm/arm64_armv8_linux_clang_ubuntu1804/dpdk/config/ppc/ppc64le-power8-linux-gcc-ubuntu1804

8fd9b631 - ci: switch to Ubuntu 20.04

Fri, 06 May 2022 11:00:00 +0000

ci: switch to Ubuntu 20.04Ubuntu 18.04 is now rather old.Besides, other entities in our CI are also testing this distribution.Switch to a newer Ubuntu release and benefit from more recenttool(chain)s: for example, net/cnxk now builds fine and can bere-enabled.Note: Ubuntu 18.04 and 20.04 seem to preserve the same paths for the ARMand PPC cross compilation toolchains, so we can use a singleconfiguration file (with the hope, future releases of Ubuntu will do thesame).Signed-off-by: David Marchand Acked-by: Aaron Conole Reviewed-by: Ruifeng Wang List of files: /dpdk/config/arm/arm64_armv8_linux_clang_ubuntu/dpdk/config/ppc/ppc64le-power8-linux-gcc-ubuntu

3cba7ced - sched: remove vector functions

Tue, 22 Feb 2022 12:00:00 +0000

sched: remove vector functionsRemove RTE_SCHED_VECTOR flag from rte_config.h.This flag is no longer useful. Only scalar version is supported.Signed-off-by: Megha Ajmera Acked-by: Cristian Dumitrescu List of files: /dpdk/config/arm/meson.build

d91c4b1b - sched: enable traffic class oversubscription unconditionally

Tue, 22 Feb 2022 12:00:00 +0000

sched: enable traffic class oversubscription unconditionallyRemoved RTE_SCHED_SUBPORT_TC_OV from rte_config.h.Best effort traffic class oversubscription is always enabled.Signed-off-by: Megha Ajmera Acked-by: Cristian Dumitrescu List of files: /dpdk/config/rte_config.h

b2b3858a - devtools: add ppc64 in meson build test

Sun, 14 Jun 2020 22:00:00 +0000

devtools: add ppc64 in meson build testAdd cross-compilation support of a PPC target in the build test matrix.The CPU is defined as Power8, running as little endian.Signed-off-by: Thomas Monjalon Reviewed-by: David Christensen List of files: /dpdk/config/ppc/ppc64le-power8-linux-gcc

ab5ac1ad - config/x86: fix MinGW cross build with Meson 0.49

Fri, 12 Nov 2021 21:00:00 +0000

config/x86: fix MinGW cross build with Meson 0.49Cross build with MinGW was broken for the baseline meson 0.49.2.Cause: in c_args = '-mno-avx512f' from config/x86/cross-mingw,each character was treated as a separate compiler option: meson.build:4:0: ERROR: Compiler x86_64-w64-mingw32-gcc can not compile programs.With c_args = ['-mno-avx512f'] configuration passed, but build failed,because Meson placed -mno-avx512f after -mavx512f in CFLAGS: In file included from /usr/lib/gcc/x86_64-w64-mingw32/9.3-win32/include/immintrin.h:55, from /usr/lib/gcc/x86_64-w64-mingw32/9.3-win32/include/x86intrin.h:32, from ../dpdk/lib/net/net_crc_avx512.c:13: /usr/lib/gcc/x86_64-w64-mingw32/9.3-win32/include/avx512fintrin.h:1650:1: error: inlining failed in call to always_inline _mm512_ternarylogic_epi64: target specific option mismatch 1650 | _mm512_ternarylogic_epi64 (__m512i __A, __m512i __B, __m512i __C, | ^~~~~~~~~~~~~~~~~~~~~~~~~ ../dpdk/lib/net/net_crc_avx512.c:59:9: note: called from here 59 | return _mm512_ternarylogic_epi64(tmp0, tmp1, data_block, 0x96); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Additionally, -m[no-]avx512f flag is expected to be in machine_argsby all the checks in meson.build files.Commit 419c6e9af69e ("net/i40e: fix build for Windows MinGW")fixed the errors cause by MinGW using AVX512F on Windows.The binutils AVX512F bug check is now portable,so enable it for Windows to switch AVX512 support on and offwithout any special logic for MinGW.Fixes: 549bfc83168f ("config: disable AVX512 with MinGW")Signed-off-by: Dmitry Kozlyuk Acked-by: Bruce Richardson List of files: /dpdk/config/x86/cross-mingw

ecb904cc - build: fix warnings when running external commands

Thu, 20 Jan 2022 18:00:00 +0000

build: fix warnings when running external commandsMeson 0.61.1 is giving warnings that the calls to run_command do notalways explicitly specify if the result is to be checked or not, i.e.there is a missing "check" parameter. This is because the defaultbehaviour without the parameter is due to change in the future.We can fix these warnings by explicitly adding into each call whetherthe result should be checked by meson or not. This patch thereforeadds in "check: false" to each run_command call where the result isbeing checked by the DPDK meson.build code afterwards, and adds in"check: true" to any calls where the result is currently unchecked.Bugzilla ID: 921Cc: stable@dpdk.orgReported-by: Jerin Jacob Signed-off-by: Bruce Richardson Tested-by: Jerin Jacob List of files: /dpdk/config/x86/meson.build

d832326a - build: fix warning about using -Wextra flag

Fri, 21 Jan 2022 16:00:00 +0000

build: fix warning about using -Wextra flagEach build, meson would issue a warning reporting that the"warning_level" setting should be used in place of adding -Wextradirectly to our build commands. Testing with meson 0.61 shows that theonly difference for gcc and clang builds between warning levels 1 and2 is the addition of -Wextra, so we can remove the warning by deletingour explicit set of Wextra and changing the build defaults towarning_level 2.Fixes: 524a0d5d66b9 ("build: enable extra warnings with meson")Signed-off-by: Bruce Richardson Acked-by: Luca Boccassi List of files: /dpdk/config/meson.build

b3fc5624 - config/ppc: fix native build with GCC 4.8.5 on RHEL 7

Wed, 03 Nov 2021 20:00:00 +0000

config/ppc: fix native build with GCC 4.8.5 on RHEL 7The POWER meson.build file incorrectly checks if the detected CPU is"greater than" POWER8 when it should actually test for "greater than orequal to" POWER8. Fixed the comparison operator.Bugzilla ID: 875Fixes: 750196880843 ("config/ppc: select instruction set for IBM Power10")Signed-off-by: David Christensen List of files: /dpdk/config/ppc/meson.build

adf93ca5 - build: increase readability via shortcut variables

Tue, 09 Apr 2019 10:00:00 +0000

build: increase readability via shortcut variablesDefine variables for "is_linux", "is_freebsd" and "is_windows"to make the code shorter for comparisons and more readable.Signed-off-by: Bruce Richardson Reviewed-by: David Marchand Acked-by: Luca Boccassi List of files: /dpdk/kernel/meson.build

1d5e58e9 - version: 22.07-rc0

Fri, 18 Mar 2022 14:00:00 +0000

version: 22.07-rc0Start a new release cycle with empty release notes.Bump version and ABI minor.Signed-off-by: David Marchand Acked-by: Thomas Monjalon Acked-by: Aaron Conole List of files: /dpdk/.travis.yml

5569dd7d - kni: allow configuring thread granularity

Thu, 20 Jan 2022 12:00:00 +0000

kni: allow configuring thread granularityThe Kni kthreads seem to be re-scheduled at a granularity of roughly1 millisecond right now, which seems to be insufficient for performingtests involving a lot of control plane traffic.Even if KNI_KTHREAD_RESCHEDULE_INTERVAL is set to 5 microseconds, itseems that the existing code cannot reschedule at the desired granularily,due to precision constraints of schedule_timeout_interruptible().In our use case, we leverage the Linux Kernel for control plane, andit is not uncommon to have 60K - 100K pps for some signaling protocols.Since we are not in atomic context, the usleep_range() function seems to bemore appropriate for being able to introduce smaller controlled delays,in the range of 5-10 microseconds. Upon reading the existing code, it wouldseem that this was the original intent. Adding sub-millisecond delays,seems unfeasible with a call to schedule_timeout_interruptible().KNI_KTHREAD_RESCHEDULE_INTERVAL 5 /* us */schedule_timeout_interruptible( usecs_to_jiffies(KNI_KTHREAD_RESCHEDULE_INTERVAL));Below, we attempted a brief comparison between the existing implementation,which uses schedule_timeout_interruptible() and usleep_range().We attempt to measure the CPU usage, and RTT between two Kni interfaces,which are created on top of vmxnet3 adapters, connected by a vSwitch.insmod rte_kni.ko kthread_mode=single carrier=onschedule_timeout_interruptible(usecs_to_jiffies(5))kni_single CPU Usage: 2-4 %[root@localhost ~]# ping 1.1.1.2 -I eth1PING 1.1.1.2 (1.1.1.2) from 1.1.1.1 eth1: 56(84) bytes of data.64 bytes from 1.1.1.2: icmp_seq=1 ttl=64 time=2.70 ms64 bytes from 1.1.1.2: icmp_seq=2 ttl=64 time=1.00 ms64 bytes from 1.1.1.2: icmp_seq=3 ttl=64 time=1.99 ms64 bytes from 1.1.1.2: icmp_seq=4 ttl=64 time=0.985 ms64 bytes from 1.1.1.2: icmp_seq=5 ttl=64 time=1.00 msusleep_range(5, 10)kni_single CPU usage: 50%64 bytes from 1.1.1.2: icmp_seq=1 ttl=64 time=0.338 ms64 bytes from 1.1.1.2: icmp_seq=2 ttl=64 time=0.150 ms64 bytes from 1.1.1.2: icmp_seq=3 ttl=64 time=0.123 ms64 bytes from 1.1.1.2: icmp_seq=4 ttl=64 time=0.139 ms64 bytes from 1.1.1.2: icmp_seq=5 ttl=64 time=0.159 msusleep_range(20, 50)kni_single CPU usage: 24%64 bytes from 1.1.1.2: icmp_seq=1 ttl=64 time=0.202 ms64 bytes from 1.1.1.2: icmp_seq=2 ttl=64 time=0.170 ms64 bytes from 1.1.1.2: icmp_seq=3 ttl=64 time=0.171 ms64 bytes from 1.1.1.2: icmp_seq=4 ttl=64 time=0.248 ms64 bytes from 1.1.1.2: icmp_seq=5 ttl=64 time=0.185 msusleep_range(50, 100)kni_single CPU usage: 13%64 bytes from 1.1.1.2: icmp_seq=1 ttl=64 time=0.537 ms64 bytes from 1.1.1.2: icmp_seq=2 ttl=64 time=0.257 ms64 bytes from 1.1.1.2: icmp_seq=3 ttl=64 time=0.231 ms64 bytes from 1.1.1.2: icmp_seq=4 ttl=64 time=0.143 ms64 bytes from 1.1.1.2: icmp_seq=5 ttl=64 time=0.200 msusleep_range(100, 200)kni_single CPU usage: 7%64 bytes from 1.1.1.2: icmp_seq=1 ttl=64 time=0.716 ms64 bytes from 1.1.1.2: icmp_seq=2 ttl=64 time=0.167 ms64 bytes from 1.1.1.2: icmp_seq=3 ttl=64 time=0.459 ms64 bytes from 1.1.1.2: icmp_seq=4 ttl=64 time=0.455 ms64 bytes from 1.1.1.2: icmp_seq=5 ttl=64 time=0.252 msusleep_range(1000, 1100)kni_single CPU usage: 2%64 bytes from 1.1.1.2: icmp_seq=1 ttl=64 time=2.22 ms64 bytes from 1.1.1.2: icmp_seq=2 ttl=64 time=1.17 ms64 bytes from 1.1.1.2: icmp_seq=3 ttl=64 time=1.17 ms64 bytes from 1.1.1.2: icmp_seq=4 ttl=64 time=1.17 ms64 bytes from 1.1.1.2: icmp_seq=5 ttl=64 time=1.15 msUpon testing, usleep_range(1000, 1100) seems roughly equivalent inlatency and cpu usage to the variant with schedule_timeout_interruptible(),while usleep_range(100, 200) seems to give a decent tradeoff betweenlatency and cpu usage, while allowing users to tweak the limits forimproved precision if they have such use cases.Disabling RTE_KNI_PREEMPT_DEFAULT, interestingly seems to lead to asoftlockup on my kernel.Kernel panic - not syncing: softlockup: hung tasksCPU: 0 PID: 1226 Comm: kni_single Tainted: G W O 3.10 #1 [] dump_stack+0x19/0x1b [] panic+0xcd/0x1e0 [] watchdog_timer_fn+0x160/0x160 [] __run_hrtimer.isra.4+0x42/0xd0 [] hrtimer_interrupt+0xe7/0x1f0 [] smp_apic_timer_interrupt+0x67/0xa0 [] apic_timer_interrupt+0x6d/0x80This patch also attempts to remove this option.References:[1] https://www.kernel.org/doc/Documentation/timers/timers-howto.txtSigned-off-by: Tudor Cornea Acked-by: Padraig Connolly Reviewed-by: Ferruh Yigit List of files: /dpdk/kernel/linux/kni/kni_dev.h

ea6b39b5 - kni: remove ethtool support

Fri, 24 May 2019 16:00:00 +0000

kni: remove ethtool supportCurrent design requires kernel drivers and they need to be probed byLinux up to some level so that they can be usable by DPDK for ethtoolsupport, this requires maintaining the Linux drivers in DPDK.Also ethtool support is limited and hard, if not impossible, to expandto other PMDs.Since KNI ethtool support is not used commonly, if not used at all,removing the support for the sake of simplicity and maintenance.Signed-off-by: Ferruh Yigit Acked-by: Stephen Hemminger Acked-by: Neil Horman Acked-by: Thomas Monjalon List of files: /dpdk/kernel/linux/kni/Kbuild

c28e2165 - kni: fix build for SLES15-SP3

Tue, 19 Oct 2021 10:00:00 +0000

kni: fix build for SLES15-SP3As suse version numbering is inconsistent to determine Linux kernelAPI to be used. In this patch we check parameter of 'ndo_tx_timeout'API directly from the kernel source. This is done only for suse build.Bugzilla ID: 812Cc: stable@dpdk.orgSigned-off-by: Aman Singh Acked-by: Ferruh Yigit Tested-by: Longfeng Liang List of files: /dpdk/kernel/linux/kni/compat.h