git:master:3b0ffe28: modules: readme files regenerated - auth ... [skip ci]

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

git:master:3b0ffe28: modules: readme files regenerated - auth ... [skip ci]

Kamailio Dev
Module: kamailio
Branch: master
Commit: 3b0ffe28df3590d76d985d18b9f3b3b0bf9ce056
URL: https://github.com/kamailio/kamailio/commit/3b0ffe28df3590d76d985d18b9f3b3b0bf9ce056

Author: Kamailio Dev <[hidden email]>
Committer: Kamailio Dev <[hidden email]>
Date: 2017-06-14T13:46:27+02:00

modules: readme files regenerated - auth ... [skip ci]

---

Modified: src/modules/auth/README

---

Diff:  https://github.com/kamailio/kamailio/commit/3b0ffe28df3590d76d985d18b9f3b3b0bf9ce056.diff
Patch: https://github.com/kamailio/kamailio/commit/3b0ffe28df3590d76d985d18b9f3b3b0bf9ce056.patch

---

diff --git a/src/modules/auth/README b/src/modules/auth/README
index a89538a5b6..51ba685b48 100644
--- a/src/modules/auth/README
+++ b/src/modules/auth/README
@@ -429,19 +429,19 @@ modparam("auth", "one_time_nonce", 1)
    size).
 
    Instead of using single arrays for keeping nonce state, these arrays
-   can be divided into more partitions. Each ser process is assigned to
-   one of these partitions, allowing for higher concurrency on multi-CPU
-   machines. Besides increasing performance, increasing nid_pool_no has
-   also a negative effect: it could decrease the maximum supported
-   in-flight nonces in certain conditions. In the worst case, when only
-   one ser process receives most of the traffic (e.g. very busy tcp
-   connection between two proxies), the in-flight nonces could be limited
-   to the array size (nc_array_size for nonce_count or otn_in_flight_no
-   for one_time_nonce) divided by the partitions number (nid_pool_no).
-   However for normal traffic, when the process receiving a message is
-   either random or chosen in a round-robin fashion the maximum in-flight
-   nonces number will be very little influenced by nid_pool_no (the
-   messages will be close to equally distributed to processes using
+   can be divided into more partitions. Each Kamailio process is assigned
+   to one of these partitions, allowing for higher concurrency on
+   multi-CPU machines. Besides increasing performance, increasing
+   nid_pool_no has also a negative effect: it could decrease the maximum
+   supported in-flight nonces in certain conditions. In the worst case,
+   when only one Kamailio process receives most of the traffic (e.g. very
+   busy tcp connection between two proxies), the in-flight nonces could be
+   limited to the array size (nc_array_size for nonce_count or
+   otn_in_flight_no for one_time_nonce) divided by the partitions number
+   (nid_pool_no). However for normal traffic, when the process receiving a
+   message is either random or chosen in a round-robin fashion the maximum
+   in-flight nonces number will be very little influenced by nid_pool_no
+   (the messages will be close to equally distributed to processes using
    different partitions).
 
    nid_pool_no value should be one of: 1, 2, 4, 8, 16, 32 or 64 (the


_______________________________________________
Kamailio (SER) - Development Mailing List
[hidden email]
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev