Also to add to this, any memory access violation caused by any thread of one app will cause crash of entire OSv instance bringing second app down as well. Other similar types of error situations would apply as well.
Waldek On Thursday, November 15, 2018 at 7:21:32 AM UTC-5, Francesco Iadanza wrote: > > Hi Nadah, > I see, so the problem could raise in case of concurrent access to system > features that are not protected (for example) with locks. > > Thanks for the clarification > > F. > > Il giorno gio 15 nov 2018, 13:00 Nadav Har'El <[email protected] > <javascript:>> ha scritto: > >> On Thu, Nov 15, 2018 at 12:17 PM Francesco Iadanza <[email protected] >> <javascript:>> wrote: >> >>> Hi, >>> my question was just to identify the limitations and understand better >>> the architecture. >>> So, from what I understood, the ELF namespaces feature means that having >>> multiple instance of the same app (in threads, of course) is very likely >>> going to crash due to the possible use of the same symbols >>> >> >> No, the "ELF namespace" feature is what allows multiple copies of the >> same application to run concurrently *without* running into problems when >> using the same symbols, because each will be run in a separate "name space" >> of symbols, so the global variable called "a" in one copy of the >> application will be separate from a global variable also called "a" in a >> second copy. >> >> >>> or maybe even worse, not crash but work not as expected (app1 calling >>> functionA from app2 instead of app1). >>> >> >> Again, the ELF namespace feature solves exactly this problem. >> >> > -- You received this message because you are subscribed to the Google Groups "OSv Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
