GitLab

This adds a new component E2ESimbricksNetwork to the end-to-end
framework, which allows to connect to other simulated networks through
Simbricks.

This avoids issues for parameter strings containing characters that are
treated specially while parsing the arguments, e.g. whitespace.

Instead of passing all parameters using the command line, we write them
first into a file and then pass the filename to the end-to-end
framework.

Use the new basic building blocks SwitchNode and SimpleChannel in the
ns3 end-to-end framework to build topologies.

This adds support for configuring and running simulations using the ns3
end-to-end framework.

This temporarily drops support for DDIO and the L3 cache.

ExpEnv hd_path and hd_path_raw use absolute path unmodified if given as param

Update to newer ns-3 version and adapt code for changes (mostly
renamed files and command line parameters) in the ns-3 submodule.

This change is mostly about the default semantics of asyncio.wait(). It
doesn't forward any exceptions that are raised by any of the coroutines
it waits for. This effectively causes exceptions to be swallowed. In
contrast, asyncio.gather() forwards exceptions to its calling coroutine.

The reason we didn't spot this earlier is that exceptions were swallowed
by the call to `asyncio.wait()` in
`runners.py:ExperimentBaseRunner.terminate_collect_sims()` when invoking
`int_term_kill()`. Instead, we now use `asyncio.gather()`, which
forwards exceptions to the calling coroutine.

Currently --repo, which is used to find simulators etc., defaults to '..',
which only works when executing in the 'experiments' directory in the simbricks
repo. Instead we make this relative to the run.py-file's path.

So far, simulator instances not connected to any other instances were
skipped accidentally when creating the graph.

Currently, when a checkpoint is created in gem5 using the KVM CPU, the
simulated tick when the checkpoint is taken will end up in the few
seconds or more when the KVM CPU is slow. When the checkpoint is
afterwards restored, gem5 will continue the simulation at this tick.
This means that other, synchronized simulators first have to catch up,
essentially just synchronizing without performing any useful work.
Depending on their speed, this can take a lot of time and is especially
costly with a RTL simulator in the loop. To avoid this we now, by
default, edit the to be restored gem5 checkpoint to start at tick 0
instead.

There are now no more inline functions and a proper main function
instead of top-level code. Functionality-wise, nothing was changed. Code
was only rearranged and some comments added.

Starting with Python3.11, asyncio.wait() doesn't accept coroutines anymore. Instead, we have to wrap every coroutine in a tasks.

These all do the same thing except with different hosts or NICs. Combine them
in one script running all configurations.
- gem5_i40e_pair
- qemu_i40e_pair
- qemu_e1000_pair

Helps quickly determine available CPU features in host simulators.