Kevin,
I've been reviewing and testing this code and found something odd. The
measured processing cycles are
always zero in my setup.
sample log output:
2017-08-08T12:48:25.871Z|00417|dpif_netdev|INFO|Core 6 on numa node 0 assigned
port 'port-em2' rx queue 5 (measured processing cycles 10011304791).
2017-08-08T12:48:25.871Z|00418|dpif_netdev|INFO|Core 6 on numa node 0 assigned
port 'port-em2' rx queue 4 (measured processing cycles 0).
Initially I configure my setup with 16 rxq's and a PMD CPU mask of 0x1FFFE.
Then I've been testing by running
iperf traffic with multiple ports 8 or 16 (-P option) to allow 'processing
cycles' to count up. Or at least I think that's
what should be happening. But when I reconfigure the rxq's and cpu mask the
processing cycles is always
zero.
How are you testing this? Perhaps it's just my test harness or something else.
Initial setup:
ovs-vsctl set Interface port-em2 options:n_rxq=16
ovs-vsctl set Open_vSwitch . other_config:pmd-cpu-mask=0x1FFFE
(Note that I do not set affinity - I have read your patch to infer that this is
for cases without affinitization.)
After getting traffic I then run this setup:
ovs-vsctl set Interface port-em2 options:n_rxq=4
ovs-vsctl set Open_vSwitch . other_config:pmd-cpu-mask=0x1E
Any advice or comment?
Thanks,
- Greg