d/numam-dpdk
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
0f5df4ea5d
numam-dpdk/meson_options.txt

45 lines
2.7 KiB
Meson
Raw Normal View History

build: fix options ordering Sort the options alphabetically and make a note of the preferred order at the top of the file. Signed-off-by: Chas Williams <3chas3@gmail.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-07 15:53:18 +00:00
# Please keep these options sorted alphabetically.
build: add header includes check To verify that all DPDK headers are ok for inclusion directly in a C file, and are not missing any other pre-requisite headers, we can auto-generate for each header an empty C file that includes that header. Compiling these files will throw errors if any header has unmet dependencies. For some libraries, there may be some header files which are not for direct inclusion, but rather are to be included via other header files. To allow later checking of these files for missing includes, we separate out the indirect include files from the direct ones. To ensure ongoing compliance, we enable this build test as part of the default x86 build in "test-meson-builds.sh". Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2021-01-29 16:48:21 +00:00
option('check_includes', type: 'boolean', value: false,
description: 'build "chkincs" to verify each header file can compile alone')
build: enable a developer mode setting To allow support for additional build checks and tests only really relevant for developers, we add support for a developer mode option to DPDK. The default, "auto", value for this enables developer mode if a ".git" folder is found at the root of the source tree - as was the case with the previous "make" build system. There is also support for explicitly enabling or disabling this option using "meson configure" if so desired. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2021-02-25 15:29:01 +00:00
option('developer_mode', type: 'feature',
description: 'turn on additional build checks relevant for DPDK developers')
build: support disabling drivers with meson Add support for a new build option to turn off certain drivers. Any other drivers which depend on the one being disabled will also be disabled with a suitable debug message. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: Luca Boccassi <bluca@debian.org> Acked-by: Maxime Coquelin <maxime.coquelin@redhat.com>
2019-09-25 14:55:31 +00:00
option('disable_drivers', type: 'string', value: '',
description: 'Comma-separated list of drivers to explicitly disable.')
build: add option to override drivers install directory Allow users and packagers to override the default dpdk/drivers subdirectory where the PMDs get installed under $lib. Signed-off-by: Luca Boccassi <bluca@debian.org> Acked-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: Timothy Redaelli <tredaelli@redhat.com>
2018-10-02 16:20:46 +00:00
option('drivers_install_subdir', type: 'string', value: 'dpdk/pmds-<VERSION>',
description: 'Subdirectory of libdir where to install PMDs. Defaults to using a versioned subdirectory.')
build: generate API documentation with meson Signed-off-by: Luca Boccassi <bluca@debian.org> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2018-09-11 20:42:36 +00:00
option('enable_docs', type: 'boolean', value: false,
description: 'build documentation')
config: enable/disable drivers in Arm builds Add support for enabling or disabling drivers for Arm cross build. Do not implement any enable/disable lists yet. Enabling drivers is useful when building for an SoC where we only want to build a few drivers. That way the list won't be too long. Similarly, disabling drivers is useful when we want to disable only a few drivers. Both of these are advantageous mainly in aarch64 -> aarch64 (or arch -> same arch) builds, where the build machine may have the required driver dependencies, yet we don't want to build drivers for a specific SoC. If enable_drivers is a non-empty list, build only those drivers, otherwise build all drivers and add them to enable_drivers. If disable_drivers is non-empty list, build all drivers specified in enable_drivers except those in disable_drivers. There are two drivers, bus/pci and bus/vdev, which break the build if not enabled. Address this by always enabling these if the user disables them or doesn't specify in their allowlist. Also remove the old Makefile arm configuration options which don't do anything in Meson. Signed-off-by: Juraj Linkeš <juraj.linkes@pantheon.tech> Reviewed-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com> Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2021-04-14 13:41:34 +00:00
option('enable_drivers', type: 'string', value: '',
description: 'Comma-separated list of drivers to build. If unspecified, build all drivers.')
ethdev: install driver headers Introduce a meson option 'enable_driver_sdk', when true installs internal driver headers for ethdev. This allows drivers that do not depend on stable api/abi to be built external to the dpdk source tree. Signed-off-by: Tyler Retzlaff <roretzla@linux.microsoft.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
2021-03-12 22:20:06 +00:00
option('enable_driver_sdk', type: 'boolean', value: false,
description: 'Install headers to build drivers.')
config: disable Linux kernel modules by default Based on the techboard meeting held on 2019-11-06, It's been decided to disable all kmods by default from v20.02. http://mails.dpdk.org/archives/dev/2019-November/151763.html Signed-off-by: Jerin Jacob <jerinj@marvell.com>
2020-01-17 19:14:00 +00:00
option('enable_kmods', type: 'boolean', value: false,
build: fix options ordering Sort the options alphabetically and make a note of the preferred order at the top of the file. Signed-off-by: Chas Williams <3chas3@gmail.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-07 15:53:18 +00:00
description: 'build kernel modules')
examples: build some samples with meson Add support for having selected example apps built as part of a meson, ninja build. By default none are built, and those to be built should be named directly in the -Dexamples='' meson configuration argument. This is useful for developers working on a feature who want to use a suitable example, or examples, to test that feature, as they can compile everything up in one go, and run the example without having to do a ninja install first. This commit adds examples which don't consist of multiple apps in subdirectories to the meson build, so they can be built by default by passing -Dexamples parameter to meson. Not included are the following examples: * ethtool * multi-process * netmap_compat * performance-thread * quota_watermark * server_node_efd * vm_power_manager To test the apps added here, use the following command, merged to one line, to add them to your meson build (command to be run inside the build directory): meson configure -Dexamples=bbdev_app,bond,cmdline,distributor,\ eventdev_pipeline_sw_pmd, exception_path,helloworld,\ ip_fragmentation,ip_pipeline,ip_reassembly, ipsec-secgw,\ ipv4_multicast,kni,l2fwd-cat,l2fwd-crypto,l2fwd-jobstats,\ l2fwd-keepalive,l2fwd,l3fwd-acl,l3fwd-power,l3fwd-vf,l3fwd,\ link_status_interrupt,load_balancer,packet_ordering,ptpclient,\ qos_meter,qos_sched,rxtx_callbacks,skeleton,tep_termination,\ timer,vhost,vhost_scsi,vmdq,vmdq_dcb Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Reviewed-by: Luca Boccassi <bluca@debian.org>
2017-09-12 15:42:02 +00:00
option('examples', type: 'string', value: '',
description: 'Comma-separated list of examples to build by default')
baseband/turbo_sw: support meson build Turbo_sw PMD driver now building with meson/ninja with or without SDK libraries. Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com> Acked-by: Kamil Chalupnik <kamilx.chalupnik@intel.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
2019-06-19 17:48:38 +00:00
option('flexran_sdk', type: 'string', value: '',
description: 'Path to FlexRAN SDK optional Libraries for BBDEV device')
net/mlx: add static ibverbs linkage with meson The libibverbs (and libmlx4/5) can be statically embedded in the shared PMD library, or in the application with the static PMD. It was supported with make build system in commit 2c0dd7b69fb0 ("config: add static linkage of mlx dependency"). The same feature is enabled with meson when using pkg-config (i.e. only if the call to dependency() is successful). The fallback method for searching library with cc.find_library() is not supported because the dependencies of the found library would not be linked (no such info in .a file unlike .so). The main difference, in meson build system, is the generated .pc file giving arguments to link DPDK with the application. Unfortunately the .pc file will not keep memory of the static linkage option for libibverbs. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2020-02-12 22:07:04 +00:00
option('ibverbs_link', type: 'combo', choices : ['static', 'shared', 'dlopen'], value: 'shared',
description: 'Linkage method (static/shared/dlopen) for Mellanox PMDs with ibverbs dependencies.')
build: sort meson options alphabetically Wrap each entry at the description value to avoid really long lines also. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: Luca Boccassi <bluca@debian.org>
2017-09-20 10:28:55 +00:00
option('include_subdir_arch', type: 'string', value: '',
description: 'subdirectory where to install arch-dependent headers')
option('kernel_dir', type: 'string', value: '',
build: support KNI cross-compilation The KNI linux module is using a custom target for building, which doesn't take into account any cross compilation arguments. The arguments in question are ARCH, CROSS_COMPILE (for gcc, clang) and CC, LD (for clang). Get those from the cross file and pass them to the custom target. The user supplied path may not contain the 'build' directory, such as when using cross-compiled headers, so only append that in the default case (when no path is supplied in native builds) and use the unmodified path from the user otherwise. Also modify the install path accordingly. Signed-off-by: Juraj Linkeš <juraj.linkes@pantheon.tech> Reviewed-by: Bruce Richardson <bruce.richardson@intel.com>
2021-02-11 12:59:46 +00:00
description: 'Path to the kernel for building kernel modules. Headers must be in $kernel_dir or $kernel_dir/build. Modules will be installed in /lib/modules.')
build: sort meson options alphabetically Wrap each entry at the description value to avoid really long lines also. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: Luca Boccassi <bluca@debian.org>
2017-09-20 10:28:55 +00:00
option('machine', type: 'string', value: 'native',
build: alias default build as generic The current machine='default' build name is not descriptive. The actual default build is machine='native'. Add an alternative string which does the same build and better describes what we're building: machine='generic'. Leave machine='default' for backwards compatibility. Signed-off-by: Juraj Linkeš <juraj.linkes@pantheon.tech> Reviewed-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2021-03-30 06:40:19 +00:00
description: 'set the target machine type or "generic", a build usable on all machines of the build machine architecture or "native", which lets the compiler pick the architecture of the build machine.')
build: use integer for max ethdev ports option max_ethports was merged after the other patch was written: e04ea7fcf03c ("build: use integers for numerical options") So convert this one too like the others have already been. Fixes: d5555fc900a9 ("build: add option to override max ethdev ports") Signed-off-by: Luca Boccassi <bluca@debian.org>
2019-03-01 15:46:51 +00:00
option('max_ethports', type: 'integer', value: 32,
build: add option to override max ethdev ports Allow users and packagers to override the default RTE_MAX_ETHPORTS. This adds a new meson option, max_ethports which defaults to the current value. Signed-off-by: Chas Williams <3chas3@gmail.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-07 15:53:17 +00:00
description: 'maximum number of Ethernet devices')
build: use integers for numerical options Now that the minimum Meson version has been bumped past 0.45 we can use integer as an option type directly. Signed-off-by: Luca Boccassi <bluca@debian.org> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 17:46:36 +00:00
option('max_lcores', type: 'integer', value: 128,
build: sort meson options alphabetically Wrap each entry at the description value to avoid really long lines also. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: Luca Boccassi <bluca@debian.org>
2017-09-20 10:28:55 +00:00
description: 'maximum number of cores/threads supported by EAL')
config: increase default maximum number of NUMA nodes AMD CPU can present a high number of NUMA nodes. On a dual-socket with 16 CCXs per CPU, the option "CCX (or LLC) as NUMA domain" will expose 32 NUMA nodes. The DPDK default should be 32 for better compatibility. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: Jerin Jacob <jerinj@marvell.com> Reviewed-by: Asaf Penso <asafp@nvidia.com>
2021-02-03 21:08:50 +00:00
option('max_numa_nodes', type: 'integer', value: 32,
build: sort meson options alphabetically Wrap each entry at the description value to avoid really long lines also. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: Luca Boccassi <bluca@debian.org>
2017-09-20 10:28:55 +00:00
description: 'maximum number of NUMA nodes supported by EAL')
config/arm: add platform config option Add Arm SoC configuration sets to Arm meson.build and add an arch agnostic meson option, 'platform', to select from these SoC configurations for meson native builds. This is preferable to specifying a cross file when doing aarch64 -> aarch64 builds, since the cross file specifies the toolchain as well. Signed-off-by: Juraj Linkeš <juraj.linkes@pantheon.tech> Reviewed-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com> Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com> Tested-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
2021-04-14 13:41:35 +00:00
option('platform', type: 'string', value: '',
description: 'use configuration for a particular platform (such as a SoC).')
trace: introduce new subsystem Define the public API for trace support. This patch also adds support for the build infrastructure and update the MAINTAINERS file for the trace subsystem. The 8 bytes tracepoint object is a global variable, and can be used in fast path. Created a new __rte_trace_point section to store the tracepoint objects as, - It is a mostly read-only data and not to mix with other "write" global variables. - Chances that the same subsystem fast path variables come in the same fast path cache line. i.e, it will enable a more predictable performance number from build to build. Signed-off-by: Jerin Jacob <jerinj@marvell.com> Signed-off-by: Sunil Kumar Kori <skori@marvell.com> Acked-by: David Marchand <david.marchand@redhat.com>
2020-04-22 19:03:19 +00:00
option('enable_trace_fp', type: 'boolean', value: false,
description: 'enable fast path trace points.')
test: build app with meson as dpdk-test This patch enables the test/test app to be built. It also adds the test binary to be a meson-test, which allows the meson test infrastructure to be used to run tests. Tests are listed using the same test binary, however each test sets a different DPDK_TEST environment variable. The string contents of this DPDK_TEST env var is entered in the command line interface. As such, the familiar test names such as "ring_perf_autotest" etc are valid tests to run using this meson test infrastructure. Note that the tests are run serially, given that we cannot run multiple primary processes at a time. As each test must initialize EAL this takes some time depending on the number of hugepages. In future, we could improve this to run multiple tests from one EAL init, but it is out of scope for this patchset. Finally, an option to build the tests is added to the meson build options. When disabled, the unit test code in test/test is not compiled. The default is set to 'true'. To disable, run: $ meson configure -Dtests=false Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2017-12-20 11:16:32 +00:00
option('tests', type: 'boolean', value: true,
description: 'build unit tests')
build: fix options ordering Sort the options alphabetically and make a note of the preferred order at the top of the file. Signed-off-by: Chas Williams <3chas3@gmail.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-07 15:53:18 +00:00
option('use_hpet', type: 'boolean', value: false,
description: 'use HPET timer in EAL')
Reference in New Issue Copy Permalink