Hi Lukasz,
> I've just pushed v3 with minor fixes and mbuf performance tests. There are 6 > very simple tests: > * alloc_free allocates and frees mbufs from/to mempool one by one > * bulk_alloc_free does the same but in bulks > * data_manipulation uses few functions containing sanity checks > (is_contiguous, append, trim, prepend, adj) > * sanity_checks_without_header runs robust sanity checks (with header > parameter = 0) > * sanity_checks_with_header does full sanity checks (with header parameter = > 1) > * sanity_checks_with_header_in_chain does the same as above, but all mbufs > are chained into single list. > I run those tests in 3 different compilations: > * debug without_rte_log_can_log - sanity checks not empty, but without > runtime checks of rte_log_can_log > * debug with_rte_log_can_log - debug enabled and runtime checks used > * no debug - debug mode disabled - sanity checks are empty macros Do we have data when debug was enabled at build-time (RTE_DEBUG is on), but was disabled at run-time (rte_log_can_log() will return zero for mbuf functions)? That the situation I was concerned about. Konstantin
