Few remarks here ...

As a matter of fact, if an external library doesn't require shared memory, leave it as it is, without enforcing Kamailio's pkg memory.

I looked over time to several libs used by different Kamailio modules, most of them are using anyhow malloc/free for what is not expected to be shared memory. Also, I found that is not easy to predict how much private memory an external lib may need, so that is impacted if enforcing pkg, resulting bad runtime behaviour. We actually never tried to enforce pkg to external libs (e.g., like mysql or postgres clients, redis/mongodb, ...).

If needed to use shared memory, then it is a must to set our shm memory manager for external libs. We have to do it for TLS, because the connections are shared among Kamailio workers.

Otherwise, PKG must be used for the code written in Kamailio.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.