Evan Hunt 6936db2f59 Always use the number of CPUS for resolver->ntasks ... Since the fctx hash table is now self-resizing, and resolver tasks are selected to match the thread that created the fetch context, there shouldn't be any significant advantage to having multiple tasks per CPU; a single task per thread should be sufficient. Additionally, the fetch context is always pinned to the calling netmgr thread to minimize the contention just to coalesced fetches - if two threads starts the same fetch, it will be pinned to the first one to get the bucket.		2022-05-19 09:27:33 +02:00
..
bind9	prevent a possible buffer overflow in configuration check	2022-05-13 19:59:58 -07:00
dns	Always use the number of CPUS for resolver->ntasks	2022-05-19 09:27:33 +02:00
irs	Update the copyright information in all files in the repository	2022-01-11 09:05:02 +01:00
isc	Always use the number of CPUS for resolver->ntasks	2022-05-19 09:27:33 +02:00
isccc	Keep the list of scheduled events on the timer	2022-04-01 23:45:23 +02:00
isccfg	Rename "hostname" to "remote-hostname" within "tls"	2022-05-03 17:15:43 +03:00
ns	Cleanup dns_message_gettemp*() functions - they cannot fail	2022-05-17 12:39:25 +02:00
.gitignore	The isc/platform.h header has been completely removed	2021-07-06 05:33:48 +00:00
Makefile.am	move samples/resolve.c to bin/tests/system	2021-04-16 14:29:43 +02:00
unit-test-driver.sh.in	Update the copyright information in all files in the repository	2022-01-11 09:05:02 +01:00