Run the Traffic
- Execute the Netperf TCP RR test between the servers' VMs. To configure and run the Netperf , follow the steps in the subsections of Testing ADQ with Netperf.
- Watch the busy_poll counters on the host machine.
watch -d -n 0.5 "ethtool -S $iface | grep busy | column" - Inspect the pollers on the host machine.
When ADQ application traffic is running with one or more independent pollers configured, system monitoring tools such as top/htop will show kernel threads running (with kernel version 5.12+). Refer to Verify ADQ Application Traffic and Independent Pollers (If Applicable) for more information.
Note:Application traffic can be pinned either to the same CPU cores, or different cores, than the independent poller threads. There may be slight performance improvements using different CPU cores for the kernel pollers. However, if reducing the total number of CPU cores used by ADQ is important, overlapping application threads and independent poller threads is an option.
Known Issues
Egress traffic does not go from the last queue of the ADQ TC set; this is a kernel-specific issue that has been addressed in the 5.19* kernel.