dev September 2022

passt-dev@passt.top

4 participants
44 discussions

[PATCH 00/11] Improve command dispatch in test scripts
by David Gibson 02 Sep '22

02 Sep '22

The test scripts need to dispatch commands in various different contexts: on the host, in namespaces, and in guests. Currently this is done by running each context in a tmux pane and simulating typing into that pane using tmux commands. This has a number of problems: * It's slow * Getting the results from programs is tricky and error prone. We can misparse output if: * The window isn't large enough * Commands produce output which looks like a shell prompt * The shell doesn't have the prompt we expect * A accidental keypress while the tests are running can mess up the test run * We have to issue explicit "echo $?" commands to check if things succeeded This series adds a new subsystem to the test scripts for dispatching commands which accurately preserves output (both stdout and stderr), and exit codes. Most of the testsuite is converted to this new system. For now the distro tests still rely on the old approach, since they have some complications that require additional handling. That does, alas, mean we have some ugly transitional code remaining. Oh well, we should be able to clean that up at some point. This series is pased on the previous series cleaning up the performance tests. David Gibson (11): test: Correctly match "background" with "wait" commands test: Context execution helpers test: Allow a tmux pane to watch commands executed in contexts test: Integration of old-style pane execution and new context execution test: Issue host commands via context for most tests test: Use new-style contexts for passt pane in the pasta and passt tests test: Add nsholder utility test: Extend context system to run commands in namespace for pasta tests test: Use context system for guest commands test: Use context system for two_guests tests test: Use new-style command issue for passt_in_ns tests test/.gitignore | 3 + test/Makefile | 13 +- test/lib/context | 127 ++++++++++++++++++ test/lib/layout | 58 +++----- test/lib/setup | 274 +++++++++++++++++++------------------- test/lib/term | 84 ++++++++++++ test/lib/test | 138 ++++++++----------- test/nsholder.c | 117 ++++++++++++++++ test/passt.mbuto | 32 ++++- test/run | 1 + test/shutdown/passt | 4 +- test/shutdown/passt_in_ns | 4 +- test/tcp/passt | 2 + test/tcp/passt_in_ns | 17 ++- test/tcp/pasta | 1 - test/udp/passt | 1 + test/udp/passt_in_ns | 5 +- test/udp/pasta | 1 - 18 files changed, 608 insertions(+), 274 deletions(-) create mode 100644 test/lib/context create mode 100644 test/nsholder.c -- 2.37.2

1 11

[PATCH 0/4] Cleanups to performance tests
by David Gibson 01 Sep '22

01 Sep '22

A handful of changes to the performance tests to make them more robust and faster. David Gibson (4): gitignore pidfiles other than passt.pid test: Combine iperf3c and iperf3s into a single DSL command test: Parameterize run time for throughput performance tests test: Rewrite test_iperf3 .gitignore | 3 +- test/lib/test | 113 +++++++++++++++++++------------------------- test/perf/passt_tcp | 68 ++++++++++---------------- test/perf/passt_udp | 63 +++++++++--------------- test/perf/pasta_tcp | 59 +++++++++-------------- test/perf/pasta_udp | 61 ++++++++++-------------- 6 files changed, 143 insertions(+), 224 deletions(-) -- 2.37.2

1 4

[PATCH 0/8] Allow pasta to take a command to spawn instead of shell
by David Gibson 01 Sep '22

01 Sep '22

When not attaching to an existing network namespace, pasta always spawns an interactive shell in a new namespace to attach to. Most commands which can issue a shell in a modified environment can also issue other commands as well (e.g. env, strace). We want to allow pasta to do the same. Because of the way the non-option argument to pasta is currently overloaded, allowing this requires some other changes to the way we parse the command line. David Gibson (8): conf: Make the argument to --pcap option mandatory conf: Use "-D none" and "-S none" instead of missing empty option arguments Correct manpage for --userns Remove --nsrun-dir option Move ENOENT error message into conf_ns_opt() More deterministic detection of whether argument is a PID, PATH or NAME Use explicit --netns option rather than multiplexing with PID Allow pasta to take a command to execute conf.c | 269 +++++++++++++++++++++++++++++--------------------------- passt.1 | 54 ++++++------ pasta.c | 33 ++++--- pasta.h | 2 +- pcap.c | 28 ------ 5 files changed, 191 insertions(+), 195 deletions(-) -- 2.37.2

2 17

[PATCH] test/README: Requirements for socket buffer sizes and hardware performance events
by Stefano Brivio 01 Sep '22

01 Sep '22

Performance tests use iperf3(1) with large windows, and these sysctl entries are needed to run them unmodified. The passt demo uses perf(1) to report syscall overhead, and that needs access to hardware performance counters for unprivileged users. Reported-by: David Gibson <david(a)gibson.dropbear.id.au> Signed-off-by: Stefano Brivio <sbrivio(a)redhat.com> --- test/README.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/test/README.md b/test/README.md index 581949a..72a4986 100644 --- a/test/README.md +++ b/test/README.md @@ -47,6 +47,22 @@ Virtual machine images are built during test executions using [mbuto](https://mbuto.lameexcu.se/), the shell script is sourced via _git_ as needed, so there's no need to actually install it. +### Kernel parameters + +Performance tests use iperf3 with rather large TCP receiving and sending +windows, to decrease the likelihood of iperf3 itself becoming the bottleneck. +These values need to be allowed by the kernel of the host running the tests. +Example for /etc/sysctl.conf: + + net.core.rmem_max = 134217728 + net.core.wmem_max = 134217728 + +Further, the passt demo uses perf(1), relying on hardware events for performance +counters, to display syscall overhead. The kernel needs to allow unprivileged +users to access these events. Suggested entry for /etc/sysctl.conf: + + kernel.perf_event_paranoid = -1 + ### Special requirements for continuous integration and demo modes Running the test suite as continuous integration or demo modes will record the -- 2.35.1

2 1

2024

2023

2022

2021

dev September 2022