> From: Morten Brørup [mailto:m...@smartsharesystems.com] > Sent: Monday, 7 October 2024 13.46 > > Some applications want to omit the trace feature. > Either to reduce the memory footprint, to reduce the exposed attack > surface, or for other reasons. > > This patch adds an option in rte_config.h to include or omit trace in > the > build. Trace is included by default. > > Omitting trace works by omitting all trace points. > For API and ABI compatibility, the trace feature itself remains. > > Furthermore, a public function to determine if trace is build time > enabled > is added; mainly for the benefit of the dpdk-test application. > > Signed-off-by: Morten Brørup <m...@smartsharesystems.com> > Acked-by: Stephen Hemminger <step...@networkplumber.org> > Acked-by: Jerin Jacob <jer...@marvell.com> > ---
Both trace_autotest and trace_perf_autotest have been tested (in a Linux environment) to behave as expected, both with and without RTE_TRACE defined. Tested-by: Morten Brørup <m...@smartsharesystems.com>
