On 2024-09-12 09:35, Jerin Jacob wrote:
On Wed, Sep 11, 2024 at 11:08 PM Mattias Rönnblom
<mattias.ronnb...@ericsson.com> wrote:
Add test suite to exercise the <rte_lcore_var.h> API.
Signed-off-by: Mattias Rönnblom <mattias.ronnb...@ericsson.com>
Acked-by: Morten Brørup <m...@smartsharesystems.com>
--
RFC v5:
* Adapt tests to reflect the removal of the GET() and SET() macros.
RFC v4:
* Check all lcore id's values for all variables in the many variables
test case.
* Introduce test case for max-sized lcore variables.
RFC v2:
* Improve alignment-related test coverage.
---
app/test/meson.build | 1 +
app/test/test_lcore_var.c | 432 ++++++++++++++++++++++++++++++++++++++
2 files changed, 433 insertions(+)
create mode 100644 app/test/test_lcore_var.c
diff --git a/app/test/meson.build b/app/test/meson.build
index e29258e6ec..48279522f0 100644
--- a/app/test/meson.build
+++ b/app/test/meson.build
@@ -103,6 +103,7 @@ source_file_deps = {
'test_ipsec_sad.c': ['ipsec'],
'test_kvargs.c': ['kvargs'],
'test_latencystats.c': ['ethdev', 'latencystats', 'metrics'] +
sample_packet_forward_deps,
+ 'test_lcore_var.c': [],
'test_lcores.c': [],
'test_link_bonding.c': ['ethdev', 'net_bond',
+}
+
+REGISTER_FAST_TEST(lcore_var_autotest, true, false, test_lcore_var);
IMO, Good to add one perf test suite for the operations like other
library calls. It may be compared with TLS on same operation.
So that end users can decide to use the scheme based on their use
case, and we get performance test case to avoid future regression
for this library.
OK. I've added a micro benchmark.
It may not show any difference in numbers, but once we have self
monitoring performance counters[1] it can in the future.
[1[]
https://patches.dpdk.org/project/dpdk/patch/20230201131757.1787527-1-tduszyn...@marvell.com/
--
2.34.1
