<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=us-ascii"> <meta name="Generator" content="Microsoft Exchange Server"> <style></style> </head> <body> <meta content="text/html; charset=UTF-8"> <style type="text/css" style="">  </style> <div dir="ltr"> <div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Helvetica,sans-serif"> <p>Yes, exactly.</p> <p><br> </p> <p>Best Regards,</p> <div id="x_Signature"> <div name="x_divtagdefaultwrapper" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:; margin:0"> Christopher Wong <div><br> </div> </div> </div> </div> <hr tabindex="-1" style="display:inline-block; width:98%"> <div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Lennart Poettering <lennart@poettering.net><br> <b>Sent:</b> Thursday, March 10, 2022 2:52:38 PM<br> <b>To:</b> Christopher Wong<br> <b>Cc:</b> systemd-devel@lists.freedesktop.org<br> <b>Subject:</b> Re: [systemd-devel] PrivateNetwork=yes is memory costly</font> <div> </div> </div> </div> <font size="2"><span style="font-size:10pt;"> <div class="PlainText">On Do, 10.03.22 11:50, Christopher Wong (Christopher.Wong@axis.com) wrote:<br> <br> > Hi Lennart,<br> ><br> ><br> > It is definitely a functionality we want to use. However, the memory came as an unexpected side effect. Since we are not only enabling this for one single service, instead we are applying it globally for all services.<br> ><br> > Now due to this huge memory consumption we are trying to put<br> > everything into the same namespace using<br> > JoinsNamespaceOf=<some-service>. It seems to consume less memory.<br> <br> This means they will still be isolated from the network, but no longer<br> from each other.<br> <br> Lennart<br> <br> --<br> Lennart Poettering, Berlin<br> </div> </span></font> </body> </html>