a9de470cc7
Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
28 lines
788 B
C
28 lines
788 B
C
/* SPDX-License-Identifier: BSD-3-Clause
|
|
* Copyright(c) 2010-2016 Intel Corporation
|
|
*/
|
|
|
|
/* Test prototypes */
|
|
int test_table_stub_combined(void);
|
|
int test_table_lpm_combined(void);
|
|
int test_table_lpm_ipv6_combined(void);
|
|
#ifdef RTE_LIBRTE_ACL
|
|
int test_table_acl(void);
|
|
#endif
|
|
int test_table_hash8unoptimized(void);
|
|
int test_table_hash8lru(void);
|
|
int test_table_hash8ext(void);
|
|
int test_table_hash16unoptimized(void);
|
|
int test_table_hash16lru(void);
|
|
int test_table_hash16ext(void);
|
|
int test_table_hash32unoptimized(void);
|
|
int test_table_hash32lru(void);
|
|
int test_table_hash32ext(void);
|
|
int test_table_hash_cuckoo_combined(void);
|
|
|
|
/* Extern variables */
|
|
typedef int (*combined_table_test)(void);
|
|
|
|
extern combined_table_test table_tests_combined[];
|
|
extern unsigned n_table_tests_combined;
|