Rework the tests to check the correct layer in a single test. Factor
out tests for reuse in other modules. Extend the test suite for
libalias(3) to incoming connections. Test the various types of
redirections.
gettimeofday(3) is almost as expensive as the calls to libalias.
So the call frequency for this call is reduced by a factor of 1000 in
order to neglect it's influence.
Using NAT entries became more realistic: A communication of a random
length of up to 150 packets (10% outgoing, 90% incoming) is applied
for each entry.
Add port forwardings to the performance tests. This will cause random
incoming packets to match the random port forwardings opends beforehand.
After a long test run, a lot of ressouces have been allocated.
Measure the time tot free them.
Reviewed by: kp (partially)
Differential Revision: https://reviews.freebsd.org/D30412
Differential Revision: https://reviews.freebsd.org/D30408
Differential Revision: https://reviews.freebsd.org/D30405
Differential Revision: https://reviews.freebsd.org/D30443
(cherry picked from commit f1462ab051)
(cherry picked from commit 755bab6d55)
(cherry picked from commit 6e87898a2c)
(cherry picked from commit d62e1ecba0)
(cherry picked from commit 5434ebd256)
Fix various bugs:
(cherry picked from commit ccac04cae5)
(cherry picked from commit 7b8696bf12)
(cherry picked from commit fef99da69f)
(cherry picked from commit f4c460dacd)
Due to the new, external performance test utility, the regular test
suite can reduce the stress test to a fair amount of activity.
(cherry picked from commit a660948b7b)
In order to modify libalias for performance, the existing
functionality must not change. Enforce this.
Testing LibAliasOut functionality. This concentrates the typical use
case of initiating data transfers from the inside. Provide a
exhaustive test for the data structure in order to check for
performance improvements.
In order to compare upcoming changes for their effectivness, measure
performance by counting opertions and the runtime of each operation
over the time. Accumulate all tests in a single instance, so make it
complicated over the time. If you wait long enough, you will notice
the expiry of old flows.
Reviewed by: kp
Differential Revision: https://reviews.freebsd.org/D30307
Differential Revision: https://reviews.freebsd.org/D30335
Differential Revision: https://reviews.freebsd.org/D30379
(cherry picked from commit 7fd8baee75)
(cherry picked from commit c1fbb54f4b)
(cherry picked from commit 33c1bdfc3e)
