From: Mark Andrews Date: Tue, 14 Sep 2021 06:02:46 +0000 (+1000) Subject: document 'masterfile-format map' vs 'vm.max_map_count' X-Git-Tag: v9.16.22~4^2 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=f6e66e94f0b31df70f51b6bd13e862637758fe1e;p=thirdparty%2Fbind9.git document 'masterfile-format map' vs 'vm.max_map_count' --- diff --git a/doc/arm/reference.rst b/doc/arm/reference.rst index a455609b101..9b58e0a6990 100644 --- a/doc/arm/reference.rst +++ b/doc/arm/reference.rst @@ -6478,6 +6478,11 @@ some cases to convert ``map`` files to ``text`` format using ``named-compilezone`` before an upgrade, then back to ``map`` format with the new version of ``named-compilezone`` afterward.) +The use of ``map`` format may also be limited by operating system +mmap(2) limits like ``sysctl vm.max_map_count``. For Linux, this +defaults to 65536, which limits the number of mapped zones that can +be used without increasing ``vm.max_map_count``. + ``raw`` format uses network byte order and avoids architecture- dependent data alignment so that it is as portable as possible, but it is still primarily expected to be used inside the same single system. To