Is there any specific reason why shared memory can be configured via the config files ("shm_mem_size") AND CLI flags ("-m") but package memory can only be set via CLI flags ("-M")?
Did no one ever came across the need to configure the package memory limit so far, or is there another way to achieve it without using the CLI flag?
Hello,
config parsing requires pkg to be initialized.
Also, for shm there are some internal triggers that can initialize it (as it starts to be needed), so a matter of where is your shm_mem_size, might no longer be used, so it safer to set shm size via cli param.
Cheers, Daniel
On 05.09.23 08:49, Ivan Ribakov wrote:
Hello,
the main cause for this is that the private “package” memory pool is per process, and the first process that is started already needs to initialize its pool to the proper size and allocate some memory in it. So, from a programming point of view it would be more difficult to implement if we need to later change the private/PKG pool size again while using it already. Like after parsing the configuration file or at a similar stage.
The shared memory pool is initialized at a later stage, and not much needed during the startup phase of the server. Therefore, this is easier to do with the configuration file.
Cheers,
Henning
-- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.comhttps://gilawa.com/
From: Ivan Ribakov i.ribakov@zaleos.net Sent: Dienstag, 5. September 2023 08:49 To: sr-users@lists.kamailio.org Subject: [SR-Users] Configuring package memory
Is there any specific reason why shared memory can be configured via the config files ("shm_mem_size") AND CLI flags ("-m") but package memory can only be set via CLI flags ("-M")?
Did no one ever came across the need to configure the package memory limit so far, or is there another way to achieve it without using the CLI flag?
-- Ivan Ribakov Software Engineer www.zaleos.nethttp://www.zaleos.net/
[Image removed by sender.]
-
Daniel-Constantin Mierla -
Henning Westerholt -
Ivan Ribakov