[4.1] 616e1b5 Clarified the documentation on vsm_overflow[ed]

[Lasse Karstensen]

commit 616e1b5790192d4205cd7f6002d72e7f7016612f
Author: Pål Hermunn Johansen <hermunn at varnish-software.com>
Date:   Wed Mar 9 16:38:29 2016 +0100

    Clarified the documentation on vsm_overflow[ed]
    
    In most circumstances the counters vsm_overflow and vsm_overflowed
    should be zero. This patch tells the user what he should probably do
    when they are not.

diff --git a/include/tbl/vsc_f_main.h b/include/tbl/vsc_f_main.h
index 94341b5..13106f4 100644
--- a/include/tbl/vsc_f_main.h
+++ b/include/tbl/vsc_f_main.h
@@ -629,6 +629,8 @@ VSC_F(vsm_overflow,		uint64_t, 0, 'g', 'B', diag,
 	"Number of bytes which does not fit"
 	" in the shared memory used to communicate"
 	" with tools like varnishstat, varnishlog etc."
+	" If this counter is not zero, consider"
+	" increasing the runtime variable vsm_space."
 )
 
 VSC_F(vsm_overflowed,		uint64_t, 0, 'c', 'B', diag,
@@ -636,4 +638,6 @@ VSC_F(vsm_overflowed,		uint64_t, 0, 'c', 'B', diag,
 	"Total number of bytes which did not fit"
 	" in the shared memory used to communicate"
 	" with tools like varnishstat, varnishlog etc."
+	" If this counter is not zero, consider"
+	" increasing the runtime variable vsm_space."
 )