From: Hangbin Liu <liuhangbin@gmail.com>
To: lvs-devel@vger.kernel.org
Cc: netdev@vger.kernel.org,
Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
Julian Anastasov <ja@ssi.bg>, Hangbin Liu <liuhangbin@gmail.com>
Subject: [PATCHv2 net-next 1/4] ipvs: fix sync_threshold description and add sync_refresh_period, sync_retries
Date: Mon, 20 Feb 2017 16:31:35 +0800 [thread overview]
Message-ID: <1487579498-18967-2-git-send-email-liuhangbin@gmail.com> (raw)
In-Reply-To: <1487579498-18967-1-git-send-email-liuhangbin@gmail.com>
Fix sync_threshold description which should have two values. Also add
sync_refresh_period and sync_retries based on commit 749c42b620a9
("ipvs: reduce sync rate with time thresholds").
Signed-off-by: Hangbin Liu <liuhangbin@gmail.com>
---
Documentation/networking/ipvs-sysctl.txt | 40 +++++++++++++++++++++++++-------
1 file changed, 31 insertions(+), 9 deletions(-)
diff --git a/Documentation/networking/ipvs-sysctl.txt b/Documentation/networking/ipvs-sysctl.txt
index e6b1c02..7acaaa6 100644
--- a/Documentation/networking/ipvs-sysctl.txt
+++ b/Documentation/networking/ipvs-sysctl.txt
@@ -185,15 +185,37 @@ secure_tcp - INTEGER
The value definition is the same as that of drop_entry and
drop_packet.
-sync_threshold - INTEGER
- default 3
-
- It sets synchronization threshold, which is the minimum number
- of incoming packets that a connection needs to receive before
- the connection will be synchronized. A connection will be
- synchronized, every time the number of its incoming packets
- modulus 50 equals the threshold. The range of the threshold is
- from 0 to 49.
+sync_threshold - vector of 2 INTEGERs: sync_threshold, sync_period
+ default 3 50
+
+ It sets synchronization threshold, which is the minimum number
+ of incoming packets that a connection needs to receive before
+ the connection will be synchronized. A connection will be
+ synchronized, every time the number of its incoming packets
+ modulus sync_period equals the threshold. The range of the
+ threshold is from 0 to sync_period.
+
+ When sync_period and sync_refresh_period are 0, send sync only
+ for state changes or only once when pkts matches sync_threshold
+
+sync_refresh_period - UNSIGNED INTEGER
+ default 0
+
+ In seconds, difference in reported connection timer that triggers
+ new sync message. It can be used to avoid sync messages for the
+ specified period (or half of the connection timeout if it is lower)
+ if connection state is not changed since last sync.
+
+ This is useful for normal connections with high traffic to reduce
+ sync rate. Additionally, retry sync_retries times with period of
+ sync_refresh_period/8.
+
+sync_retries - INTEGER
+ default 0
+
+ Defines sync retries with period of sync_refresh_period/8. Useful
+ to protect against loss of sync messages. The range of the
+ sync_retries is from 0 to 3.
snat_reroute - BOOLEAN
0 - disabled
--
2.5.5
next prev parent reply other threads:[~2017-02-20 8:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 6:33 [PATCH net 0/4] update ipvs sysctl document Hangbin Liu
2017-02-17 6:33 ` [PATCH net 1/4] ipvs: fix sync_threshold description and add sync_refresh_period, sync_retries Hangbin Liu
2017-02-17 6:33 ` [PATCH net 2/4] ipvs: Document sysctl sync_qlen_max and sync_sock_size Hangbin Liu
2017-02-17 6:34 ` [PATCH net 3/4] ipvs: Document sysctl sync_ports Hangbin Liu
2017-02-17 6:34 ` [PATCH net 4/4] ipvs: Document sysctl pmtu_disc Hangbin Liu
2017-02-19 14:04 ` [PATCH net 0/4] update ipvs sysctl document Julian Anastasov
2017-02-20 8:19 ` Hangbin Liu
2017-02-20 8:31 ` [PATCHv2 net-next " Hangbin Liu
2017-02-20 8:31 ` Hangbin Liu [this message]
2017-02-20 8:31 ` [PATCHv2 net-next 2/4] ipvs: Document sysctl sync_qlen_max and sync_sock_size Hangbin Liu
2017-02-20 8:31 ` [PATCHv2 net-next 3/4] ipvs: Document sysctl sync_ports Hangbin Liu
2017-02-20 8:31 ` [PATCHv2 net-next 4/4] ipvs: Document sysctl pmtu_disc Hangbin Liu
2017-02-21 20:01 ` [PATCHv2 net-next 0/4] update ipvs sysctl document Julian Anastasov
2017-03-13 9:14 ` Simon Horman
2017-03-15 2:42 ` Hangbin Liu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1487579498-18967-2-git-send-email-liuhangbin@gmail.com \
--to=liuhangbin@gmail.com \
--cc=ja@ssi.bg \
--cc=lvs-devel@vger.kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).