git:master:f5561aa3: modules: readme files regenerated - pipelimit ... [skip ci]
Module: kamailio Branch: master Commit: f5561aa35928e04e8ddc2f853dba4a040a51ab05 URL: https://github.com/kamailio/kamailio/commit/f5561aa35928e04e8ddc2f853dba4a04... Author: Kamailio Dev <kamailio.dev@kamailio.org> Committer: Kamailio Dev <kamailio.dev@kamailio.org> Date: 2026-10-08T08:46:09+02:00 modules: readme files regenerated - pipelimit ... [skip ci] --- Modified: src/modules/pipelimit/README --- Diff: https://github.com/kamailio/kamailio/commit/f5561aa35928e04e8ddc2f853dba4a04... Patch: https://github.com/kamailio/kamailio/commit/f5561aa35928e04e8ddc2f853dba4a04... --- diff --git a/src/modules/pipelimit/README b/src/modules/pipelimit/README index 99ce78671f7..26a7b90471d 100644 --- a/src/modules/pipelimit/README +++ b/src/modules/pipelimit/README @@ -160,13 +160,14 @@ Chapter 1. Admin Guide The Random Early Detection Algorithm tries to circumvent the synchronization problem imposed by the tail drop algorithm by measuring - the average load and adapting the drop rate dynamically. When running - with the RED algorithm (enabled by default) Kamailio will return errors - to the Kamailio routing engine every n'th packet trying to evenly - spread the measured load of the last timer interval onto the current - interval. As a negative side effect Kamailio might drop messages - although the limit might not be reached within the interval. Decrease - the timer interval if you encounter this. + the average CPU load and adapting the drop rate dynamically. When + running with the RED algorithm (enabled by default) Kamailio will + return errors to the Kamailio routing engine every n'th packet trying + to evenly spread the measured load of the last timer interval onto the + current interval. As a negative side effect Kamailio might drop + messages although the limit might not be reached within the interval. + Decrease the timer interval if you encounter this. It requires + load_fetch bit 1 set (value 1). Network Algorithm (NETWORK) @@ -174,7 +175,8 @@ Chapter 1. Admin Guide The total amount of bytes waiting to be consumed on all the network interfaces is retrieved once every timer_interval seconds. If the returned amount exceeds the limit specified in the modparam, pl_check() - returns false (negative value). + returns false (negative value). It requires load_fetch bit 2 set (value + 2). Feedback Algorithm (FEEDBACK) @@ -325,14 +327,16 @@ modparam("pipelimit", "timer_mode", 1) 4.9. load_fetch (integer) Control if the module should fetch the load for CPU and network - traffic. If set to 0, no load is fetched; if set to 1, the load is - fetched every timer interval. + traffic. If set to 0, no load is fetched; if bit 1 is set to 1 (value + 1), the CPU load is fetched every timer interval; if bit 2 is set to 1 + (value 2), the network load is fetched every timer interval. It can be + set to value 3 to fetch both CPU and network loads. - Default value is 1. + Default value is 0. Example 1.9. Set load_fetch parameter ... -modparam("pipelimit", "load_fetch", 0) +modparam("pipelimit", "load_fetch", 3) ... 4.10. reply_code (integer)
I’d pay attention to this when upgrading or reviewing an existing Kamailio configuration. If load_fetch is left at the new default of 0, CPU- or network-based limiting may no longer behave as expected. Using 3 is appropriate when both measurements are needed, while 1 or 2 lets you avoid collecting the other metric. This is more than a README wording change because the documented defaults and configuration semantics have changed. https://cargamesfree.io
participants (2)
-
Kamailio Dev -
miredtravel@gmail.com