Ondřej Surý c8f1fa0e47 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> (cherry picked from commit 5a2df8caf5)		2024-09-03 14:54:40 +02:00
..
check	Use EXIT_SUCCESS and EXIT_FAILURE	2024-08-06 15:19:06 +02:00
confgen	Use EXIT_SUCCESS and EXIT_FAILURE	2024-08-06 15:19:06 +02:00
delv	make "max_restarts" a configurable value	2024-08-07 15:36:15 -07:00
dig	check for NULL before closing batchfp	2024-08-21 21:37:51 -07:00
dnssec	Use EXIT_SUCCESS and EXIT_FAILURE	2024-08-06 15:19:06 +02:00
named	Use clang-format-19 to update formatting	2024-08-22 10:25:22 +02:00
nsupdate	Use EXIT_SUCCESS and EXIT_FAILURE	2024-08-06 15:19:06 +02:00
plugins	Remove 'inst != NULL' from cleanup check in plugin_register	2023-04-05 10:27:52 +10:00
rndc	Use EXIT_SUCCESS and EXIT_FAILURE	2024-08-06 15:19:06 +02:00
tests	Follow the number of CPU set by taskset/cpuset	2024-09-03 14:54:40 +02:00
tools	Change the NS_PER_SEC (and friends) from enum to static const	2024-08-19 15:32:03 +00:00
Makefile.am	Remove native PKCS#11 support	2021-09-09 15:35:39 +02:00