From d6f36f6c88d15b809a4478302e70949c090b0d6a Mon Sep 17 00:00:00 2001 From: Jan Hilberath Date: Mon, 4 Jan 2021 19:40:37 +0900 Subject: [PATCH] dnsdist: Fix typo in tuning documentation --- pdns/dnsdistdist/docs/advanced/tuning.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pdns/dnsdistdist/docs/advanced/tuning.rst b/pdns/dnsdistdist/docs/advanced/tuning.rst index d50becb7f7..1dd23e5063 100644 --- a/pdns/dnsdistdist/docs/advanced/tuning.rst +++ b/pdns/dnsdistdist/docs/advanced/tuning.rst @@ -48,7 +48,7 @@ To be able to use more CPU cores for UDP queries processing, it is possible to u :program:`dnsdist` will then add four identical local binds as if they were different IPs or ports, start four threads to handle incoming queries and let the kernel load balance those randomly to the threads, thus using four CPU cores for rules processing. Note that this require ``SO_REUSEPORT`` support in the underlying operating system (added for example in Linux 3.9). Please also be aware that doing so will increase lock contention and might not therefore scale linearly. -This is especially true for Lua-intensive setups, because Lua processing in dnsdist is serialized by an unique lock for all threads. +This is especially true for Lua-intensive setups, because Lua processing in dnsdist is serialized by a unique lock for all threads. Another possibility is to use the reuseport option to run several dnsdist processes in parallel on the same host, thus avoiding the lock contention issue at the cost of having to deal with the fact that the different processes will not share informations, like statistics or DDoS offenders. -- 2.47.2