[master] 26a39f2 Write up some more varnishd params in "Upgrading to 6.0".

Geoff Simmons geoff at uplex.de
Wed Mar 14 19:30:11 UTC 2018

commit 26a39f2acdf245f2dd8bb179ed78988c6ed0a889
Author: Geoff Simmons <geoff at uplex.de>
Date:   Wed Mar 14 20:28:42 2018 +0100

    Write up some more varnishd params in "Upgrading to 6.0".

diff --git a/doc/sphinx/whats-new/upgrading-6.0.rst b/doc/sphinx/whats-new/upgrading-6.0.rst
index aa551cc..b4c4ed3 100644
--- a/doc/sphinx/whats-new/upgrading-6.0.rst
+++ b/doc/sphinx/whats-new/upgrading-6.0.rst
@@ -96,7 +96,12 @@ continue using VCL 4.0.
 varnishd parameters
-XXX: ...
+The ``cli_buffer`` parameter, which was deprecated as of Varnish 5.2,
+is now retired.
+:ref:`ref_param_max_restarts` now works more correctly -- it is the
+number of ``return(restart)`` calls permitted per request. (It had
+been one less than the number of permitted restarts.)
 The parameters :ref:`ref_param_tcp_keepalive_intvl`,
 :ref:`ref_param_tcp_keepalive_probes` and
@@ -109,6 +114,15 @@ these parameters with a UDS; you may get error messages in the log for
 ``accept_filter`` or ``tcp_fastopen`` (with the VSL tag ``Error`` in
 raw grouping), but they are harmless.
+:ref:`ref_param_workspace_thread` is now used for IO buffers during
+the delivery of the client response. This space had previously been
+taken from :ref:`ref_param_workspace_client`. If you need to reduce
+memory footprint, consider reducing ``workspace_client`` by the amount
+in ``workspace_thread``.
+Added :ref:`ref_param_esi_iovs`. tl;dr: Don't touch it, unless advised
+to do so by someone familiar with the innards of Varnish.
 Changes to VCL

More information about the varnish-commit mailing list