Re: [E] Re: Inter pod communication using shared memory

From: Ion Gaztañaga (igaztanaga_at_[hidden])
Date: 2024-08-29 12:26:09

El 29/08/2024 a las 12:40, Murali Kishore escribió:
> Hi all,
> Adding to above question,
> 
> scenario details: if kubernetes pods are created in the same machine 
> with enabling shared memory so that both pods can access this shared area.
> In this case, if we run one process in pod 1 and another process in 
> pod2, and these processes are using boost interprocess to create/find 
> class objects, STL containers.
> 
> I am able to create the above scenario and run 2 pods and verified class 
> object sharing using boost interprocess library, want to check with you 
> all if there are any risks in using this way w.r.t performance and 
> stability (unexpected behaviour).
> 
> Are there any limitations/ design aspects that need to be taken care 
> while using boost library ?
> 
> Regards,
> Murali Kishore

Hi,

Glad to hear Boost.Interprocess is being used in innovative ways.

If usual shared memory (/dev/shm) between Linux containers is used, then 
I don't expect any problem and/or performance issue because there is no 
kubernetes/docker software layer between Boost.Interprocess accesses to 
mapped memory. Usual linux kernel is managing those accesses.

In any case, I've never tried using Boost.Interprocess between linux 
containers so I can't 100% guarantee everything will work fine. We'll 
try to help if something unexpected happens ;-)

Best,

Ion