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
..
dns	Always use the number of CPUS for resolver->ntasks	2022-05-19 09:27:33 +02:00
dst	Check if key metadata is modified before writing	2022-05-13 13:31:17 +02:00
.clang-format	Add separate .clang-format files for headers	2020-02-14 09:31:05 +01:00