Commit 5f07ee0d authored by Mark Andrews's avatar Mark Andrews
Browse files

Merge branch '2901-large-number-of-small-zones-in-map-format-cannot-be-loaded' into 'v9_16'

Resolve "Large number of small zones in `map` format cannot be loaded"

See merge request !5398
parents 092284b2 f6e66e94
Pipeline #84509 passed with stages
in 166 minutes and 47 seconds
...@@ -6478,6 +6478,11 @@ some cases to convert ``map`` files to ``text`` format using ...@@ -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 ``named-compilezone`` before an upgrade, then back to ``map`` format with
the new version of ``named-compilezone`` afterward.) 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- ``raw`` format uses network byte order and avoids architecture-
dependent data alignment so that it is as portable as possible, but it is 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 still primarily expected to be used inside the same single system. To
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment