This website requires JavaScript.
Explore
Help
Sign in
mirrors
/
passt
Watch
1
Star
0
Fork
You've already forked passt
0
Code
Issues
Pull requests
Projects
Releases
Packages
Wiki
Activity
Actions
8f3f8e190c
passt
/
.gitignore
11 lines
92 B
Text
Raw
Normal View
History
Unescape
Escape
Add basic .gitignore files Ignore various files generated during build or test. Reviewed-by: David Gibson <david@gibson.dropbear.id.au> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2022-05-11 09:02:51 +02:00
*~
/passt
/passt.avx2
/pasta
/pasta.avx2
/qrap
/pasta.1
/seccomp.h
test/perf: Get iperf3 stats from client side iperf3 generates statistics about its run on both the client and server sides. They don't have exactly the same information, but both have the pieces we need (AFAICT the server communicates some nformation to the client over the control socket, so the most important information is in the client side output, even if measured by the server). Currently we use the server side information for our measurements. Using the client side information has several advantages though: * We can directly wait for the client to complete and we know we'll have the output we want. We don't need to sleep to give the server time to write out the results. * That in turn means we can wrap up as soon as the client is done, we don't need to wait overlong to make sure everything is finished. * The slightly different organisation of the data in the client output means that we always want the same json value, rather than requiring slightly different onces for UDP and TCP. The fact that we avoid some extra delays speeds up the overal run of the perf tests by around 7 minutes (out of around 35 minutes) on my laptop. The fact that we no longer unconditionally kill client and server after a certain time means that the client could run indefinitely if the server doesn't respond. We mitigate that by setting 1s connect timeout on the client. This isn't foolproof - if we get an initial response, but then lose connectivity this could still run indefinitely, however it does cover by far the most likely failure cases. --snd-timeout would provide more robustness, but I've hit odd failures when trying to use it. Signed-off-by: David Gibson <david@gibson.dropbear.id.au> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
2023-11-06 08:08:27 +01:00
/c*.json
gitignore README.plain.md Add the generated README.plain.md file to .gitignore. Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2022-08-23 08:31:50 +02:00
README.plain.md
Reference in a new issue
Copy permalink