bind9/bin/tests
Ondřej Surý 5a2df8caf5 Follow the number of CPU set by taskset/cpuset
Administrators may wish to constrain the set of cores that BIND 9 runs
on via the 'taskset', 'cpuset' or 'numactl' programs (or equivalent on
other O/S), for example to achieve higher (or more stable) performance
by more closely associating threads with individual NIC rx queues. If
the admin has used taskset, it follows that BIND ought to
automatically use the given number of CPUs rather than the system wide
count.

Co-Authored-By: Ray Bellis <ray@isc.org>
2024-08-29 14:43:18 +00:00
..
startperf Reformat shell scripts with shfmt 2023-10-26 10:23:50 +02:00
system Follow the number of CPU set by taskset/cpuset 2024-08-29 14:43:18 +00:00
testdata/wire move all optional tests from bin/tests to bin/tests/optional 2018-03-09 14:12:47 -08:00
.gitignore Move environment variables from conf.sh to pytest 2024-05-09 17:08:08 +02:00
convert-trs-to-junit.py Use python3 in shebang lines for util scripts 2024-08-14 17:22:22 +02:00
Makefile.am Fix JUnit test status generator for out-of-tree system tests 2022-09-22 15:20:23 +02:00
test_client.c Use EXIT_SUCCESS and EXIT_FAILURE 2024-02-08 08:01:58 +01:00
test_server.c Use EXIT_SUCCESS and EXIT_FAILURE 2024-02-08 08:01:58 +01:00
wire_test.c Use EXIT_SUCCESS and EXIT_FAILURE 2024-02-08 08:01:58 +01:00