Changes in Makefile

11e02702 - examples: fix pkg-config override

Wed, 05 May 2021 14:25:25 +0000

examples: fix pkg-config overrideMove pkg-config override to beginning in the Makefile to allowuse PKGCONF variable to detect the libdpdk availability.Fixes: fda34680eb9a ("examples: remove legacy sections of makefiles")Cc: stable@dpdk.orgSigned-off-by: Jerin Jacob Acked-by: Bruce Richardson List of files: /dpdk/examples/l3fwd-power/Makefile

5a196330 - examples: warn about broken pkg-config

Tue, 19 Jan 2021 13:03:24 +0000

examples: warn about broken pkg-configSince the examples are designed to be built by end-users using Make, wecan detect and warn about broken pkg-config on the user's system as partof the build process.Signed-off-by: Bruce Richardson List of files: /dpdk/examples/l3fwd-power/Makefile

fda34680 - examples: remove legacy sections of makefiles

Thu, 03 Sep 2020 15:26:41 +0000

examples: remove legacy sections of makefilesThe example app makefiles contained sections using the legacy method ofcompiling with make. These are no longer needed, and are removed,leaving only the section that uses pkg-config for the make build.Signed-off-by: Ciara Power Acked-by: Nicolas Chautru List of files: /dpdk/examples/l3fwd-power/Makefile

8549295d - build/pkg-config: improve static linking flags

Tue, 30 Jun 2020 14:14:32 +0000

build/pkg-config: improve static linking flagsRather than setting -Bstatic in the linker flags when doing a static link,and then having to explicitly set -Bdynamic again afterwards, we can updatethe pkg-config file to use -l:libfoo.a syntax to explicitly refer to thestatic library in question. Since this syntax is not supported by meson'spkg-config module directly, we can post-process the .pc files instead toadjust them.Once done, we can simplify the examples' makefiles and the docs by removingthe explicit static flag.Signed-off-by: Bruce Richardson Acked-by: Luca Boccassi Acked-by: Sunil Pai G Signed-off-by: Thomas Monjalon List of files: /dpdk/examples/l3fwd-power/Makefile

eeb486f3 - eal: add telemetry as dependency

Thu, 30 Apr 2020 16:01:34 +0000

eal: add telemetry as dependencyThis patch moves telemetry further down the build, and adds it as adependency for EAL. Telemetry V2 is now configured to build by default,and the legacy support is built when the telemetry config flag is set.Telemetry now has EAL flags, shown below:"--telemetry" = Enables telemetry (this is default if no flags given)"--no-telemetry" = Disables telemetryWhen telemetry is enabled, it will attempt to open the new socketversion, and also the legacy support socket (this will depend on Janssonexternal dependency and telemetry config flag, as before).Signed-off-by: Ciara Power Signed-off-by: Bruce Richardson Reviewed-by: Keith Wiles List of files: /dpdk/examples/l3fwd-power/Makefile

a35919a1 - examples/l3fwd-power: use new telemetry

Thu, 30 Apr 2020 16:01:31 +0000

examples/l3fwd-power: use new telemetryThe l3fwd-power example app now registers a stats command withtelemetry, and provides a callback function to handle formatting thepower stats.An example usage is shown below:Connecting to /var/run/dpdk/rte/dpdk_telemetry.v2{"version": "DPDK 20.05.0-rc0", "pid": 63384, "max_output_len": 16384}--> /{"/": ["/", "/ethdev/link_status", "/ethdev/list", "/ethdev/xstats", \ "/help", "/info", "/l3fwd-power/stats", "/rawdev/list", \ "/rawdev/xstats"]}--> /l3fwd-power/stats{"/l3fwd-power/stats": {"empty_poll": 281625000, "full_poll": 0, \ "busy_percent": 0}}The existing stats tracking done by the app using the metricslibrary is unaffected. This will still be used to ensure backwardcompatibility.Signed-off-by: Bruce Richardson Signed-off-by: Ciara Power Reviewed-by: Keith Wiles List of files: /dpdk/examples/l3fwd-power/Makefile

69b1bb49 - examples: hide error for missing pkg-config path flag

Fri, 15 Nov 2019 15:17:00 +0000

examples: hide error for missing pkg-config path flagSome versions of pkg-config don't support the --path flag, which is not afatal error when building the apps. Without the flag, the makefile justcannot track the .pc file of DPDK as a dependency of the build. Therefore,we can ignore the error and suppress it by redirecting to /dev/null thestderr from that call to pkg-config.Fixes: 22119c4591a0 ("examples: use pkg-config in makefiles")Cc: stable@dpdk.orgSigned-off-by: Bruce Richardson Tested-by: Ferruh Yigit List of files: /dpdk/examples/l3fwd-power/Makefile

12a652a0 - examples: fix build with old pkg-config

Fri, 15 Nov 2019 15:16:59 +0000

examples: fix build with old pkg-configNot all versions of pkg-config in distros have support for the--define-prefix flag [1], causing errors when building examples manually orwith test-meson-builds.sh script [2].For the former case, we need to remove the hard-coded use of the flag inthe Makefiles.For the latter case, the flag is necessary for builds to succeed, so weskip the tests when it's not present, passing it as part of the pkg-configcommand if it is supported.[1]CentOS Linux release 7.7.1908 (Core)pkg-config version 0.27.1[2] ## Building cmdlineUnknown option --define-prefixgmake: Entering directory`...ild-x86-default/install-root/usr/local/share/dpdk/examples/cmdline'rm -f build/cmdline build/cmdline-static build/cmdline-sharedtest -d build && rmdir -p build || trueUnknown option --define-prefixUnknown option --define-prefixgcc -O3 main.c commands.c parse_obj_list.c -o build/cmdline-sharedmain.c:14:28: fatal error: cmdline_rdline.h: No such file or directoryFixes: ca9268529d2b ("examples: support relocated DPDK install")Fixes: 7f80a2102bbb ("devtools: test pkg-config file")Cc: stable@dpdk.orgReported-by: Ferruh Yigit Signed-off-by: Bruce Richardson Tested-by: Ferruh Yigit List of files: /dpdk/examples/l3fwd-power/Makefile

4131ad5d - examples: fix pkg-config detection with older make

Wed, 03 Jul 2019 16:40:00 +0000

examples: fix pkg-config detection with older makeMake versions before 4.2 did not have support for the .SHELLSTATUSvariable, so use another method to detect shell success.Fixes: 22119c4591a0 ("examples: use pkg-config in makefiles")Cc: stable@dpdk.orgSigned-off-by: Bruce Richardson Acked-by: Luca Boccassi List of files: /dpdk/examples/l3fwd-power/Makefile

ca926852 - examples: support relocated DPDK install

Tue, 02 Jul 2019 14:44:41 +0000

examples: support relocated DPDK installFor testing of DPDK, we want to override the prefix given by thepkg-config file, so that we can get correct paths for DPDK installedin an unusual location.Signed-off-by: Bruce Richardson Acked-by: Luca Boccassi List of files: /dpdk/examples/l3fwd-power/Makefile

609e7984 - examples/l3fwd-power: add telemetry mode

Mon, 24 Jun 2019 16:45:51 +0000

examples/l3fwd-power: add telemetry modeAdd new telemetry mode support for l3fwd-power.This is a standalone mode, in this mode l3fwd-powerdoes simple l3fwding along with calculatingempty polls, full polls, and busy percentage foreach forwarding core. The aggregation of thesevalues of all cores is reported as applicationlevel telemetry to metric library for every 500ms from themaster core.The busy percentage is calculated by recording the poll_countand when the count reaches a defined value the totalcycles it took is measured and compared with minimum and maximumreference cycles and busy rate is set according to either 0% or50% or 100%.Signed-off-by: Reshma Pattan Acked-by: Anatoly Burakov List of files: /dpdk/examples/l3fwd-power/Makefile

7e9562a1 - examples: fix make clean when using pkg-config

Fri, 17 May 2019 12:02:31 +0000

examples: fix make clean when using pkg-configThe "make clean" command had a number of issues:- the "--ignore-fail-on-non-empty" flag is not present on BSD- the call to remove the build folder would fail if there was no build folder present.These are fixed by only removing the build folder if it exists, and byusing -p flag to rmdir in place of --ignore-fail-on-non-emptyFixes: 22119c4591a0 ("examples: use pkg-config in makefiles")Cc: stable@dpdk.orgSigned-off-by: Bruce Richardson Acked-by: Luca Boccassi List of files: /dpdk/examples/l3fwd-power/Makefile

e9c65942 - examples: detect default build directory

Wed, 27 Mar 2019 13:58:05 +0000

examples: detect default build directoryMost examples have in their makefiles a default RTE_TARGET directory to beused in case RTE_TARGET is not set. Rather than just using a hard-codeddefault, we can instead detect what the build directory is relative toRTE_SDK directory.This fixes a potential issue for anyone who continues to build using"make install T=x86_64-native-linuxapp-gcc" and skips setting RTE_TARGETexplicitly, instead relying on the fact that they were building in adirectory which corresponded to the example default path - which waschanged to "x86_64-native-linux-gcc" by commit 218c4e68c1d9 ("mk: uselinux and freebsd in config names").Signed-off-by: Bruce Richardson Acked-by: Ferruh Yigit List of files: /dpdk/examples/l3fwd-power/Makefile

218c4e68 - mk: use linux and freebsd in config names

Wed, 06 Mar 2019 16:22:42 +0000

mk: use linux and freebsd in config namesRather than using linuxapp and bsdapp everywhere, we can change things touse the, more readable, terms "linux" and "freebsd" in our build configs.Rather than renaming the configs we can just duplicate the existing oneswith the new names using symlinks, and use the new names exclusivelyinternally. ["make showconfigs" also only shows the new names to keep thelist short] The result is that backward compatibility is kept fully but anynew builds or development can be done using the newer names, i.e. both"make config T=x86_64-native-linuxapp-gcc" and "T=x86_64-native-linux-gcc"work.Signed-off-by: Bruce Richardson List of files: /dpdk/examples/l3fwd-power/Makefile

742bde12 - build/linux: rename macro from LINUXAPP to LINUX

Wed, 06 Mar 2019 16:22:39 +0000

build/linux: rename macro from LINUXAPP to LINUXRename the macro to make things shorter and more comprehensible. Forboth meson and make builds, keep the old macro around for backwardcompatibility.Signed-off-by: Bruce Richardson List of files: /dpdk/examples/l3fwd-power/Makefile

a137d012 - examples/l3fwd-power: support traffic pattern aware control

Fri, 19 Oct 2018 11:07:19 +0000

examples/l3fwd-power: support traffic pattern aware controlAdd the support for new traffic pattern aware power controlpower management API.Example:./l3fwd-power -l xxx -n 4 -w 0000:xx:00.0 -w 0000:xx:00.1 -- -p 0x3-P --config="(0,0,xx),(1,0,xx)" --empty-poll="0,0,0" -l 14 -m 9 -h 1Please Reference l3fwd-power document for full parameter usageThe option "l", "m", "h" are used to set the power index forLOW, MED, HIGH power state. Only is useful after enable empty-poll--empty-poll="training_flag, med_threshold, high_threshold"The option training_flag is used to enable/disable training mode.The option med_threshold is used to indicate the empty poll thresholdof modest state which is customized by user.The option high_threshold is used to indicate the empty poll thresholdof busy state which is customized by user.Above three option default value is all 0.Once enable empty-poll. System will apply the default parameter if noother command line options are provided.If training mode is enabled, the user should ensure that no trafficis allowed to pass through the system. When training phase complete,the application transfer to normal operationSystem will start running with the modest power mode.If the traffic goes above 70%, then system will move to High power state.If the traffic drops below 30%, the system will fallback to the modestpower state.Example code use master thread to monitoring worker thread busyness.The default timer resolution is 10ms.Signed-off-by: Liang Ma Reviewed-by: Lei Yao Acked-by: David Hunt List of files: /dpdk/examples/l3fwd-power/Makefile

f88e7c17 - examples/l3fwd-power: add high/regular perf cores options

Mon, 11 Jun 2018 10:03:23 +0000

examples/l3fwd-power: add high/regular perf cores optionsAdded high/regular performance core pinning configuration optionsthat can be used in place of the existing 'config' option.'--high-perf-cores CORELIST' option allow the user to specify ahigh performance cores list; if this option is not used and the'perf-config' option is used, the application will query thesystem using the rte_power library in order to get a list ofavailable high performance cores. The cores that are consideredhigh performance are the cores that have turbo enabled.'--perf-config (port,queue,hi_perf,lcore_index)'option is similar to the existing config option, the cores are specifiedas indices for bins containing high or regular performance cores.Example:l3fwd-power -l 6,7 -- -p 0xff \--high-perf-cores 6 --perf-config="(0,0,0,0),(1,0,1,0)"cores 6 and 7 are used, core 6 is specified as a high performance core.port 0 queue 0 will use a regular performance core, index 0 (core 7)port 1 queue 0 will use a high performance core, index 0 (core 6)Signed-off-by: Radu Nicolau Acked-by: David Hunt List of files: /dpdk/examples/l3fwd-power/Makefile

ed3077c1 - examples: make Linux environment check consistent

Wed, 06 Jun 2018 13:50:27 +0000

examples: make Linux environment check consistentSome Makefiles are using CONFIG_RTE_EXEC_ENV and othersare using CONFIG_RTE_EXEC_ENV_LINUXAPP.Use the latter one for consistency.We could remove CONFIG_RTE_EXEC_ENV later if considered useless.Signed-off-by: Thomas Monjalon List of files: /dpdk/examples/l3fwd-power/Makefile

fa47405c - ethdev: remove experimental flag of ports enumeration

Tue, 24 Apr 2018 02:15:11 +0000

ethdev: remove experimental flag of ports enumerationThe basic operations for ports enumeration should not beconsidered as experimental in DPDK 18.05.The iterator RTE_ETH_FOREACH_DEV was introduced in DPDK 17.05.It uses the function the rte_eth_find_next_owned_by() to getonly ownerless ports. Its API can be considered stable.So the flag experimental is removed from rte_eth_find_next_owned_by().The flag experimental is removed from rte_eth_dev_count_avail()which is the new name of the old function rte_eth_dev_count().The flag experimental is set to rte_eth_dev_count_total()in the .c file for consistency with the declaration in the .h file.A lot of internal applications are fixed to not allow experimental API.Fixes: 8728ccf37615 ("fix ethdev ports enumeration")Fixes: d9a42a69febf ("ethdev: deprecate port count function")Fixes: e70e26861eaf ("net/mvpp2: fix build")Signed-off-by: Thomas Monjalon Tested-by: David Marchand List of files: /dpdk/examples/l3fwd-power/Makefile

8728ccf3 - fix ethdev ports enumeration

Thu, 05 Apr 2018 15:33:20 +0000

fix ethdev ports enumerationSome DPDK applications wrongly assume these requirements: - no hotplug, i.e. ports are never detached - all allocated ports are available to the applicationSuch application iterates over ports by its own mean.The most common pattern is to request the port count andassume ports with index in the range [0..count[ can be used.There are three consequences when using such wrong design: - new ports having an index higher than the port count won't be seen - old ports being detached (RTE_ETH_DEV_UNUSED) can be seen as ghosts - failsafe sub-devices (RTE_ETH_DEV_DEFERRED) will be seen by the applicationSuch mistake will be less common with growing hotplug awareness.All applications and examples inside this repository - except testpmd -must be fixed to use the iterator RTE_ETH_FOREACH_DEV.Signed-off-by: Thomas Monjalon List of files: /dpdk/examples/l3fwd-power/Makefile