|
Hi,
It seems that PrivateNetwork=yes is a memory consuming directive. The kernel seems to allocate quite an amount of memory for each service (~50 kB) that has this directive enabled. I wonder if this is expected and if anyone has had similar experience?
Is there any ways to reduce the usage?
Best Regards
Christopher Wong
|
PrivateNetwork=yes is memory costly
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: PrivateNetwork=yes is memory costly
- From: Christopher Wong <Christopher.Wong@xxxxxxxx>
- Date: Mon, 7 Mar 2022 15:10:42 +0000
- Accept-language: en-US, sv-SE
- Follow-Ups:
- Re: PrivateNetwork=yes is memory costly
- From: Lennart Poettering
- Re: PrivateNetwork=yes is memory costly
- Prev by Date: Antw: Re: [systemd‑devel] Antw: [EXT] Re: timer "OnBootSec=15m" not triggering
- Next by Date: Re: How to find out the processes systemd-shutdown is waiting for?
- Previous by thread: How to verify that my ethernet interface is really reconfigured?
- Next by thread: Re: PrivateNetwork=yes is memory costly
- Index(es):
 |