numam-dpdk/app/test-bbdev/Makefile

# SPDX-License-Identifier: BSD-3-Clause
# Copyright(c) 2017 Intel Corporation

include $(RTE_SDK)/mk/rte.vars.mk

#
# library name
#
APP = testbbdev

CFLAGS += -DALLOW_EXPERIMENTAL_API
CFLAGS += -O3
CFLAGS += $(WERROR_FLAGS)

#
# all sources are stored in SRCS-y
#
SRCS-$(CONFIG_RTE_TEST_BBDEV) += main.c
SRCS-$(CONFIG_RTE_TEST_BBDEV) += test_bbdev.c
SRCS-$(CONFIG_RTE_TEST_BBDEV) += test_bbdev_perf.c
SRCS-$(CONFIG_RTE_TEST_BBDEV) += test_bbdev_vector.c

include $(RTE_SDK)/mk/rte.app.mk
app/testbbdev: add test application for bbdev - full test suite for bbdev - test App works seamlessly on all PMDs registered with bbdev framework - a python script is provided to make our life easier - supports execution of tests by parsing Test Vector files - test Vectors can be added/deleted/modified with no need for re-compilation - various tests can be executed: (a) Throughput test (b) Offload latency test (c) Operation latency test (d) Validation test (c) Sanity checks Signed-off-by: Amr Mokhtar <amr.mokhtar@intel.com> 2018-01-11 19:23:21 +00:00			`# SPDX-License-Identifier: BSD-3-Clause`
			`# Copyright(c) 2017 Intel Corporation`

			`include $(RTE_SDK)/mk/rte.vars.mk`

			`#`
			`# library name`
			`#`
			`APP = testbbdev`

mk: add experimental tag check Add checks during build to ensure that all symbols in the EXPERIMENTAL version map section have __experimental tags on their definitions, and enable the warnings needed to announce their use. Also add an ALLOW_EXPERIMENTAL_APIS define to allow individual libraries and files to declare the acceptability of experimental api usage Signed-off-by: Neil Horman <nhorman@tuxdriver.com> Acked-by: Thomas Monjalon <thomas@monjalon.net> 2018-01-22 01:48:05 +00:00			`CFLAGS += -DALLOW_EXPERIMENTAL_API`
app/testbbdev: add test application for bbdev - full test suite for bbdev - test App works seamlessly on all PMDs registered with bbdev framework - a python script is provided to make our life easier - supports execution of tests by parsing Test Vector files - test Vectors can be added/deleted/modified with no need for re-compilation - various tests can be executed: (a) Throughput test (b) Offload latency test (c) Operation latency test (d) Validation test (c) Sanity checks Signed-off-by: Amr Mokhtar <amr.mokhtar@intel.com> 2018-01-11 19:23:21 +00:00			`CFLAGS += -O3`
			`CFLAGS += $(WERROR_FLAGS)`

			`#`
			`# all sources are stored in SRCS-y`
			`#`
			`SRCS-$(CONFIG_RTE_TEST_BBDEV) += main.c`
			`SRCS-$(CONFIG_RTE_TEST_BBDEV) += test_bbdev.c`
			`SRCS-$(CONFIG_RTE_TEST_BBDEV) += test_bbdev_perf.c`
			`SRCS-$(CONFIG_RTE_TEST_BBDEV) += test_bbdev_vector.c`

			`include $(RTE_SDK)/mk/rte.app.mk`