[master] 7d7ff24a0 Elaborate a bit on the rationale for -p max_vcl in the release docs.

[Geoff Simmons]

commit 7d7ff24a05d336b285b8234a0099d9c7e0ac7b6b
Author: Geoff Simmons <geoff at uplex.de>
Date:   Mon Sep 10 09:42:00 2018 +0200

    Elaborate a bit on the rationale for -p max_vcl in the release docs.

diff --git a/doc/sphinx/whats-new/upgrading-6.1.rst b/doc/sphinx/whats-new/upgrading-6.1.rst
index bbf1420a1..8b67d2688 100644
--- a/doc/sphinx/whats-new/upgrading-6.1.rst
+++ b/doc/sphinx/whats-new/upgrading-6.1.rst
@@ -22,11 +22,18 @@ varnishd parameters
 We have added the :ref:`ref_param_max_vcl` parameter to set a
 threshold for the number of loaded VCL programs, since it is a common
 error to let previous VCL instances accumulate without discarding
-them. The default threshold is 100, and VCL labels are not counted
-against the total. The :ref:`ref_param_max_vcl_handling` parameter
-controls what happens when you reach the limit. By default you just
-get a warning from the VCL compiler, but you can set it to refuse to
-load more VCLs, or to ignore the threshold.
+them. The remnants of undiscarded VCLs take the form of files in the
+working directory of the management process. Over time, too many of
+these may take up significant storage space, and administrative
+operations such as ``vcl.list`` may become noticeably slow, or even
+time out, when Varnish has to iterate over many files.
+
+The default threshold in :ref:`ref_param_max_vcl` is 100, and VCL
+labels are not counted against the total. The
+:ref:`ref_param_max_vcl_handling` parameter controls what happens when
+you reach the limit. By default you just get a warning from the VCL
+compiler, but you can set it to refuse to load more VCLs, or to ignore
+the threshold.
 
 Added the :ref:`ref_param_backend_local_error_holddown` and
 :ref:`ref_param_backend_remote_error_holddown` parameters. These define