Module: sip-router Branch: master Commit: 2aa02e80cd76f38e812bfddf32326248e9b74cf8 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=2aa02e80...
Author: Olle E. Johansson oej@edvina.net Committer: Olle E. Johansson oej@edvina.net Date: Sun Oct 21 18:49:43 2012 +0200
Ratelimit: Fixing typos
---
modules/ratelimit/README | 10 +++++----- modules/ratelimit/doc/ratelimit_admin.xml | 10 +++++----- 2 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/modules/ratelimit/README b/modules/ratelimit/README index 84aa33c..d8e6ebb 100644 --- a/modules/ratelimit/README +++ b/modules/ratelimit/README @@ -207,11 +207,11 @@ Chapter 1. Admin Guide
4.1. Feedback Algorithm (FEEDBACK)
- When running openser on different machines, one has to adjust the drop + When running Kamailio on different machines, one has to adjust the drop rates for the static algorithms to maintain a sub 100% load average or packets start getting dropped in the network stack. While this is not in itself difficult, it isn't neither accurate nor trivial: another - server taking a notable fraction of the cpu time will require re-tuning + server taking a notable fraction of the CPU time will require re-tuning the parameters.
While tuning the drop rates from the outside based on a certain factor @@ -226,7 +226,7 @@ Chapter 1. Admin Guide adjusted dynamically based on the load factor so that the load factor always drifts towards the specified limit (or setpoint, in PID terms).
- As reading the cpu load average is relatively expensive (opening + As reading the CPU load average is relatively expensive (opening /proc/stat, parsing it, etc), this only happens once every timer_interval seconds and consequently the FEEDBACK value is only at these intervals recomputed. This in turn makes it difficult for the @@ -421,7 +421,7 @@ modparam("ratelimit", "pipe", "4:NETWORK:10000")
8.1. rl.stats
- Lists the parameters and variabiles in the ratelimit module. + Lists the parameters and variables in the ratelimit module.
Name: rl.stats
@@ -507,7 +507,7 @@ modparam("ratelimit", "pipe", "4:NETWORK:10000")
8.8. rl.push_load
- Force the value of the load parameter. This methos is usefull for + Force the value of the load parameter. This method is useful for testing the Feedback algorithm.
Name: rl.push_load diff --git a/modules/ratelimit/doc/ratelimit_admin.xml b/modules/ratelimit/doc/ratelimit_admin.xml index 5e37fdc..5b6e40a 100644 --- a/modules/ratelimit/doc/ratelimit_admin.xml +++ b/modules/ratelimit/doc/ratelimit_admin.xml @@ -112,11 +112,11 @@ <section> <title>Dynamic Rate Limiting Algorithms</title> <para> - When running openser on different machines, one has to adjust the drop + When running &kamailio; on different machines, one has to adjust the drop rates for the static algorithms to maintain a sub 100% load average or packets start getting dropped in the network stack. While this is not in itself difficult, it isn't neither accurate nor trivial: another - server taking a notable fraction of the cpu time will require re-tuning + server taking a notable fraction of the CPU time will require re-tuning the parameters. </para> <para> @@ -136,7 +136,7 @@ in PID terms). </para> <para> - As reading the cpu load average is relatively expensive (opening /proc/stat, + As reading the CPU load average is relatively expensive (opening /proc/stat, parsing it, etc), this only happens once every timer_interval seconds and consequently the FEEDBACK value is only at these intervals recomputed. This in turn makes it difficult for the drop rate to adjust quickly. Worst case @@ -379,7 +379,7 @@ modparam("ratelimit", "pipe", "4:NETWORK:10000") <function moreinfo="none">rl.stats</function> </title> <para> - Lists the parameters and variabiles in the ratelimit module. + Lists the parameters and variables in the ratelimit module. </para> <para> Name: <emphasis>rl.stats</emphasis> @@ -542,7 +542,7 @@ modparam("ratelimit", "pipe", "4:NETWORK:10000") <function moreinfo="none">rl.push_load</function> </title> <para> - Force the value of the load parameter. This methos is usefull + Force the value of the load parameter. This method is useful for testing the Feedback algorithm. </para> <para>