On Wed, 11 Jun 2025 09:04:57 +0200
Eugenio Perez Martin
On Tue, Jun 10, 2025 at 5:29 PM Stefano Brivio
wrote: On Mon, 9 Jun 2025 11:59:21 +0200 Eugenio Perez Martin
wrote: Getting a table like [1] would give us light about this, especially if it is just a matter of running "make performance" or similar. Maybe we need to include longer queues? Focus on a given scenario? UDP goes better but TCP?
Well, it's a matter of running ./run under tests (or 'make' there). Have you tried that with your patch? It's kind of representative in the sense that it uses several message sizes and different values for the sending window.
Yes but it freezes in my env.
Copying the different windows, top-left: # tail -f --retry /home/passt/test/test_logs/context_unshare.log /home/passt/test/test_logs/context_ns.log tail: warning: --retry only effective for the initial open ==> /home/passt/test/test_logs/context_unshare.log <== unshare$ tail: cannot open '/home/passt/test/test_logs/context_ns.log' for reading: No such file or directory
[...]
=== build/cppcheck ...skipped.
=== build/clang_tidy ...skipped. ---
I guess you're missing some dependencies, nstool ('make assets', or 'make' under tests/), or similar. There's a test/README.md file listing most dependencies and also describing how to debug things, essentially: DEBUG=1 ./run and have a look at script.log. Patches for whatever issue you might be hitting in your setup are warmly welcome, of course. :) -- Stefano