aboutgitcodebugslistschat
path: root/log.c
diff options
context:
space:
mode:
authorDavid Gibson <david@gibson.dropbear.id.au>2023-11-06 18:08:30 +1100
committerStefano Brivio <sbrivio@redhat.com>2023-11-07 09:56:16 +0100
commitf94adb121afcf7d5b3cc300fccbdf2247a907f63 (patch)
tree8666362e5cf1c36c267c8be85e29a95b8a9e7371 /log.c
parent29269705239fc3102a42950a5d84c3c3acd619d0 (diff)
downloadpasst-f94adb121afcf7d5b3cc300fccbdf2247a907f63.tar
passt-f94adb121afcf7d5b3cc300fccbdf2247a907f63.tar.gz
passt-f94adb121afcf7d5b3cc300fccbdf2247a907f63.tar.bz2
passt-f94adb121afcf7d5b3cc300fccbdf2247a907f63.tar.lz
passt-f94adb121afcf7d5b3cc300fccbdf2247a907f63.tar.xz
passt-f94adb121afcf7d5b3cc300fccbdf2247a907f63.tar.zst
passt-f94adb121afcf7d5b3cc300fccbdf2247a907f63.zip
test/perf: Explicitly control UDP packet length, instead of MTU
Packet size can make a big difference to UDP throughput, so it makes sense to measure it for a variety of different sizes. Currently we do this by adjusting the MTU on the relevant interface before running iperf3. However, the UDP packet size has no inherent connection to the MTU - it's controlled by the sender, and the MTU just affects whether the packet will make it through or be fragmented. The only reason adjusting the MTU works is because iperf3 bases its default packet size on the (path) MTU. We can test this more simply by using the -l option to the iperf3 client to directly control the packet size, instead of adjusting the MTU. As well as simplifying this lets us test different packet sizes for host to ns traffic. We couldn't do that previously because we don't have permission to change the MTU on the host. Signed-off-by: David Gibson <david@gibson.dropbear.id.au> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Diffstat (limited to 'log.c')
0 files changed, 0 insertions, 0 deletions