Hi, While running L3 Fwd test case with VPP v1804 release (released yesterday), perf tool shows vlib_main() taking maximum cycles. This has been observed on Aarch64 (Both on Marvell’s Macchiatobin and Cavium’s ThunderX products) and Broadwell machine as well.
Perf top from Broadwell machine ========================= 29.72% libvlib.so.0.0.0 [.] vlib_main 17.33% dpdk_plugin.so [.] i40e_xmit_pkts 7.35% dpdk_plugin.so [.] i40e_recv_scattered_pkts_vec 7.21% libvlibmemory.so.0.0.0 [.] memclnt_queue_callback 6.02% libvnet.so.0.0.0 [.] ip4_rewrite_avx2 5.96% libvnet.so.0.0.0 [.] ip4_lookup_avx2 5.69% libvnet.so.0.0.0 [.] ip4_input_no_checksum_avx2 5.49% dpdk_plugin.so [.] dpdk_input_avx2 3.40% dpdk_plugin.so [.] dpdk_interface_tx_avx2 1.63% libvnet.so.0.0.0 [.] vnet_interface_output_node_avx2 Is this the expected behaviour? I haven’t observed vlib_main() taking max perf cycles in VPP v1801. Thanks, Nitin
