upstream/bind9
1
0
Fork 0
mirror of https://github.com/isc-projects/bind9.git synced 2026-06-11 10:29:59 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

Merge branch 'each-bufsize-doc' into 'main'

Browse source 
clarify buffer size options

See merge request isc-projects/bind9!5037
This commit is contained in:
Evan Hunt 2021-05-17 17:02:18 +00:00
commit 27386db7fe
1 changed files with 18 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

32
doc/arm/reference.rst
View file

@ -3586,22 +3586,26 @@ Tuning
milliseconds.
``tcp-recv-buffer``; ``udp-recv-buffer``
These options control the operating system receiving network buffer sizes for
TCP and UDP respectively. Buffering on the operating system level can
prevent packet drops during short spikes, but if the value is set too large
it could clog up a running server with outstanding queries that have already
timeouted. The default is ``0`` which means to use the operating system
default value. The operating system caps the maximum value that the user can
set here.
These options control the operating system's receive buffer sizes
(``SO_RCVBUF``) for TCP and UDP sockets respectively. Buffering at
the operating system level can prevent packet drops during brief load
spikes, but if the value is set too high, it could clog a running server
with outstanding queries that have already timed out. The default is
``0``, which means the operating system's default value should be used.
The minimum configurable value is ``4096``; any nonzero value lower than
that will be silently raised. The maximum value is determined by the
kernel, and values exceeding the maximum will be silently reduced.
``tcp-send-buffer``; ``udp-send-buffer``
These options control the operating system sending network buffer sizes for
TCP and UDP respectively. Buffering on the operating system level can
prevent packet drops during short spikes, but if the value is set too large
it could clog up a running server with outstanding queries that have already
timeouted. The default is ``0`` which means to use the operating system
default value. The operating system caps the maximum value that the user can
set here.
These options control the operating system's send buffer sizes
(``SO_SNDBUF``) for TCP and UDP sockets respectively. Buffering at the
operating system level can prevent packet drops during brief load
spikes, but if the value is set too high, it could clog a running server
with outstanding queries that have already timed out. The default is
``0``, which means the operating system's default value should be used.
The minimum configurable value is ``4096``; any nonzero value lower than
that will be silently raised. The maximum value is determined by the
kernel, and values exceeding the maximum will be silently reduced.
.. _builtin: